Re: Multi-branch committing in git, revisited
От | Bruce Momjian |
---|---|
Тема | Re: Multi-branch committing in git, revisited |
Дата | |
Msg-id | 201009221640.o8MGeik02211@momjian.us обсуждение исходный текст |
Ответ на | Re: Multi-branch committing in git, revisited (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Multi-branch committing in git, revisited
|
Список | pgsql-hackers |
Tom Lane wrote: > Bruce Momjian <bruce@momjian.us> writes: > > There is no need for 'git add' because once you are done you can use git > > commmit -a in each branch to add all modifications and commit them. > > git commit -a is not a universal solution. In particular, the patch > I was dealing with yesterday involved additions and removals of files, > neither of which will be implemented by git commit -a. Uh, why is that? I see -a saying: -a, --all Tell the command to automatically stage files that have been modified and deleted, butnew files you have not told git about are not affected. What is it about add/deletes that it doesn't do? Is the problem 'git add' creates a stage already? How is that a problem? -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. +
В списке pgsql-hackers по дате отправления: