On Sat, Jul 25, 2015 at 10:41:21AM -0700, Junio C Hamano wrote: > > I'm still on the fence to have the config kick in only for HEAD. > > Hmm, I cannot tell offhand if the confusion factor is worth it (I > didn't say "I don't think it is worth it"). > [...] I've snipped most of your response because it all seemed pretty reasonable to me. At this point I think I am of the opinion that the decision to use --first-parent is sufficiently nuanced that it the config option is not really a "drop-in" solution for people, even if their projects follow the matching workflow. Like you, I am not really _against_ it, but since nobody in this thread is saying "yes, I would turn that on", that may be a sign. The patch is out there on the list, and I'd encourage people who think it might be useful to apply the patch and report back in a few weeks or months if they find it useful. We _could_ merge the patch to make that experimentation easier for users. The downside is we will be stuck supporting the log.firstParent option forever, but I don't think it is actively _wrong_ to have. Just possibly useless. And poor Josh, who so nicely came to the Git table at OSCON and talked to me about his project's workflow, has now had to put up with a slew of emails and no applied patch. :) But maybe this discussion is of some use; it has not been fruitless, as I think the best answer so far is "encourage awareness and appropriate use of --first-parent". > I admit I may be minority, but two common things I do everyday are > "log --first-parent v2.5.0-rc0.." and "log --first-parent master..pu"; > I could certainly use a short-hand there. > > I already have alias for it, so this is not to help me personally, > but "log -FO" to trigger first-parent one-line would make the alias > unnecessary. I do not have an alias, but I spell it "--fir<TAB>". :) -Peff -- 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