Sam Tobin-Hochstadt <sa...@ccs.neu.edu> writes: > On Mon, May 17, 2010 at 8:33 AM, Eli Barzilay <e...@barzilay.org> wrote: >> >> >>> Possibly, it makes sense to avoid sending e-mails on merge commits, >>> but that's only a bonus. >> >> I don't think so: eg, Sam's recent merge of a long lived branch could >> have (or might have) been pushed as a single merge commit.
You mean the individual commits from that branch did not get copied to the main repo? > Further, I don't see how it would be useful to try to understand that > merge in terms of 30+ emails, all sent at the same time. I'm assuming that the granularity of your commits communicate something useful about the genesis of what you're doing - that's why we want them in the version history in the first place. If the 30+ commits can only be understood as a whole, they should be pushed as a single commit, not 30+. > Mike, do you try to read the commits on the XEmacs and Scheme48 > repositories? Of course. -- Cheers =8-} Mike Friede, Völkerverständigung und überhaupt blabla _________________________________________________ For list-related administrative tasks: http://list.cs.brown.edu/mailman/listinfo/plt-dev
