Re: erratic behavior commit --allow-empty

From: Phil Hord <phil.hord@gmail.com>
Date: Oct 4, 2012, 13:24 UTC
Message-ID: <CABURp0pgE=J9yCa+nUa7J0MZ-O-6bUHrj58zLQZ9mToh6YcOFw@mail.gmail.com>
In-Reply-To: <CAB9Jk9C4Y2LSzZW5Nkz=4f===8_gk4uAG4EKDxT17kUHu4VX1A@mail.gmail.com>

On Thu, Oct 4, 2012 at 3:07 AM, Angelo Borsotti <angelo.borsotti@gmail.com> wrote: ...

Show 12 quoted lines

> The operation that caused problems was nr. 4. In all the cases
> enlisted above, a git commit creates a brand new and unique commit
> because either it has a parent that is different from that of any
> other commit, or because its tree is different. All, except case nr 3
> when there are no binaries:
>
>      source branch         A'
>                                    :
>      topic branch        A
>
> In this case the parent is the same as that of A, i.e. none, and also
> the tree is the same.

And why is this a problem?

Is there a process or person watching the server for a new commit?

Is it not enough to notice that the pushed-to branch has a new HEAD?

Phil