Re: Multi-branch committing in git, revisited

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Multi-branch committing in git, revisited
Date: 2010-09-22 16:40:44
Message-ID: 201009221640.o8MGeik02211@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)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, but new 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(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2010-09-22 16:42:17 Re: Git cvsserver serious issue
Previous Message Bruce Momjian 2010-09-22 16:23:54 Re: Configuring synchronous replication