Re: Managing multiple branches in git
| От | David E. Wheeler |
|---|---|
| Тема | Re: Managing multiple branches in git |
| Дата | |
| Msg-id | FF521AC1-EC78-420E-9FA9-A0F01E323D68@kineticode.com обсуждение исходный текст |
| Ответ на | Re: Managing multiple branches in git (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: Managing multiple branches in git
|
| Список | pgsql-hackers |
On Jun 2, 2009, at 3:11 PM, Tom Lane wrote: > "David E. Wheeler" <david@kineticode.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
В списке pgsql-hackers по дате отправления: