On Thu, Oct 4, 2012 at 3:07 AM, Angelo Borsotti <angelo.borsotti@xxxxxxxxx> wrote: ... > 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 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html