On Wed, Aug 22, 2012 at 10:33 PM, Junio C Hamano <junio@xxxxxxxxx> wrote: > Junio C Hamano <gitster@xxxxxxxxx> writes: > >> This way we do not have to risk the list of tools go out of sync >> between the implementation and the documentation. >> >> Signed-off-by: Junio C Hamano <gitster@xxxxxxxxx> >> --- >> Junio C Hamano <gitster@xxxxxxxxx> writes: >> >>>> +--tool-help:: >>>> + List the supported and available diff tools. >>> >>> This part is a good addition (but it already is mentioned in the >>> description of --tool above, so it is more or less a "Meh"). >> >> I noticed that the main while loop has style violations in its >> case/esac, but I left it as-is. Reindenting it would be a low >> hanging fruit janitor patch that would be a separate topic. > > After hinting a low-hanging-fruit that would be an easy way for new > people to dip their toes, I saw no takers for one month, so I ended > up doing it myself. My bad, I didn't catch this and should have, especially so because I had started on style fixing mergetool last week but ditched it; I assumed it would be unwanted. I will read more carefully. Just please don't tell Charles about it ;-) (I wanted to do this a long ago but at the time we didn't have the style guide for shell, and the time was perhaps not right...) I am of course in favor of this patch. While on the mergetool topic... Would the ability to resolve the various merge situations using the command-line be a wanted addition? This would let a submodule or deleted/modified encountering user do something like: $ git mergetool --theirs -- submodule ...and not have to remember the various git commands that it runs. This could touch just the parts of mergetool that require stdin, but probably should work for everything. It seems like exposing the guts of some of these mergetool functions via command-line flags could be helpful, but I'm not sure if that's overloading mergetool with too many features. What do you think? -- David -- 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