| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Mark Mielke <mark(at)mark(dot)mielke(dot)cc>, "David E(dot) Wheeler" <david(at)kineticode(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Managing multiple branches in git |
| Date: | 2009-06-02 21:31:44 |
| Message-ID: | 19421.1243978304@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> The only reason Tom sees a single line history is because he uses an
> addon tool for CVS called cvs2cl: see <http://www.red-bean.com/cvs2cl/>.
> It's not part of CVS, and I'm not sure how many others use it. I sure
> don't.
FWIW, I believe Bruce uses some version of it as well. It's our main
tool for dredging up the raw data for release notes.
> It's written in Perl, and we have one or two tolerably competent
> Perl programmers around, so maybe we could produce a git equivalent?
It's a bit premature to speculate about alternate history tools when
we haven't figured out what the repository is going to look like. Right
at the moment I'm much more concerned about the question of supporting
a checkout-per-branch workflow. That's something I use pretty nearly
every day, whereas looking at the history is maybe a once-a-week kind
of need at most.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2009-06-02 21:33:47 | Re: Managing multiple branches in git |
| Previous Message | Ron Mayer | 2009-06-02 21:28:22 | Re: Managing multiple branches in git |