| From: | Maciek Sakrejda <msakrejda(at)truviso(dot)com> |
|---|---|
| To: | Kjetil Nygård <polpot78(at)gmail(dot)com> |
| Cc: | Craig Ringer <ringerc(at)ringerc(dot)id(dot)au>, pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: Moving to git |
| Date: | 2011-10-04 16:13:15 |
| Message-ID: | CAH_hXRYmVWD53ytwPQOB_Po1X9MkOto8wfz_D6RuXL6aTi2wZw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
>My proposal is this:
> 1. Do a git cvsimport.
> 2. Upload it to git.postgresql / github.
I'm a huge git fan, but I vehemently disagree. Fixing history after
the fact is an absolute nightmare. Dealing with broken history forever
is not fun either. *If* (ok, more realistically, *when*) we migrate,
let's do it once and do it right. If you really can't wait for it,
it's easy enough to do a git cvsimport yourself and put it up on your
own github account (then you get to deal with the problems of
different lineages when the project migrates officially).
---
Maciek Sakrejda | System Architect | Truviso
1065 E. Hillsdale Blvd., Suite 215
Foster City, CA 94404
(650) 242-3500 Main
www.truviso.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kjetil Nygård | 2011-10-04 16:25:33 | Re: Moving to git |
| Previous Message | Kjetil Nygård | 2011-10-04 15:33:44 | Re: Moving to git |