| From: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Mark Mielke <mark(at)mark(dot)mielke(dot)cc>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Managing multiple branches in git |
| Date: | 2009-06-02 22:16:19 |
| Message-ID: | FF521AC1-EC78-420E-9FA9-A0F01E323D68@kineticode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Jun 2, 2009, at 3:11 PM, Tom Lane wrote:
> "David E. Wheeler" <david(at)kineticode(dot)com> writes:
>> Perhaps there's a master repository that corresonds to CVS HEAD, and
>> then release branches are actually separate git repositories.
>
> Yeah, I was speculating about that one too. It might be workable.
> Just "cp -r" the master whenever we fork a new branch.
Well, you'd clone it, but yes, thats' what I meant.
> However, there'd
> be no very easy way to get a change history that includes patches that
> applied only to some back branches (something that does happen, a few
> times a year perhaps). Maybe that special log tool Andrew was
> speculating about would take the form of a program to aggregate the
> change histories of several repositories.
You mean so that such patches in back branches show up in the the
history of master?
Best,
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2009-06-02 22:17:36 | Re: Managing multiple branches in git |
| Previous Message | Tom Lane | 2009-06-02 22:11:16 | Re: Managing multiple branches in git |