Johannes Schindelin wrote: > Hi, > > On Fri, 6 Jun 2008, Paolo Bonzini wrote: > >>> What about people preferring the status quo? I think a command line >>> option would be in order.' >> config option seems more useful. > > Except, of course, if you have a script that wants to override whatever > the user set in her config. But can't that be just as easily done by piping through sort? (I understand there is a platform which lacks the sort utility, boohoo) Is there some legitimate function that depends on the order of listed branches (or tags)? Rather this seems like one of those things where everyone should either welcome the functionality or be indifferent to it. Adding yet another toggle for this sort of user-interface tweak seems like over-kill. It is not costless, it adds complexity to the code and to the user interface. If someone wants to list their branches alphabetically, or reverse alphabetically, or if they only want to see branches beginning with 'BUG-', why isn't it enough to just use the functionality provided by the command line? bikeshedmode = off -brandon -- 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
