| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michael Haggerty <mhagger(at)alum(dot)mit(dot)edu> |
| Cc: | Max Bowsher <maxb(at)f2s(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: git: uh-oh |
| Date: | 2010-09-06 17:56:16 |
| Message-ID: | 15373.1283795776@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Michael Haggerty <mhagger(at)alum(dot)mit(dot)edu> writes:
> Tom Lane wrote:
>> Actually, no I don't see. That sort of history might be possible in
>> some SCMs, but how is it possible in CVS? The only way to get a file
>> into a back branch is "cvs add" then "cvs commit", and the commit is
>> recorded, even if the file exactly matches what was in HEAD.
> No, it is also possible to use "cvs tag -b REL8_4_STABLE filename". In
> this case the file as it appears on the current branch is added to the
> specified branch, but CVS records no commit, author, or timestamp.
So, if we're prepared to assert that we've never done that, could we
have an option to cvs2git that is willing to use the first commit on
a branch to represent the act of adding the file to the branch?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David E. Wheeler | 2010-09-06 18:07:18 | Re: OT: OFF TOPIC: returning multiple result sets from a stored procedure |
| Previous Message | Peter Eisentraut | 2010-09-06 17:54:30 | Re: 9.1alpha1 bundled -- please verify |