Re: Managing multiple branches in git
От | David E. Wheeler |
---|---|
Тема | Re: Managing multiple branches in git |
Дата | |
Msg-id | C6E332AA-3ED2-4D21-8768-C0FA0A8AB87F@kineticode.com обсуждение исходный текст |
Ответ на | Managing multiple branches in git (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Managing multiple branches in git
Re: Managing multiple branches in git |
Список | pgsql-hackers |
On Jun 2, 2009, at 8:43 AM, Tom Lane wrote: > Each of these is configured (using --prefix) to install into a > separate > installation tree. So I can switch my attention to one branch or > another by cd'ing to the right place and adjusting a few environment > variables such as PATH and PGDATA. Yeah, with git, rather than cd'ing to another directory, you'd just do `git checkout rel8_3` and work from the same directory. > So how is this normally done with git? For better or for worse, because git is project-oriented rather than filesystem-oriented, you can't commit to all the branches at once. You have to commit to each one independently. You can push them all back to the canonical repository at once, and the canonical repository's commit hooks can trigger for all of the commits at once (or so I gather from getting emails from GitHub with a bunch of commits listed in a single message), but each commit is still independent. It has to do with the fundamentally different way in which Git works: snapshots of your code rather than different directories. Best, David
В списке pgsql-hackers по дате отправления: