Thanks! Just a couple things I noticed on a quick skim: On Thu, Apr 19, 2007 at 05:49:40PM +0200, Santi Béjar wrote: > > * use "git config" instead of directly editing config files It was a conscious decision to use a mixture of the two techniques; see, e.g., http://marc.info/?l=git&m=116994435503452&w=2 and followups. > * git branch {,-a,-r} list local, all or remote branches > > * git branch -d checkd for reachability from the current branch > > * refs/remotes/${remote}/HEAD does not depend on the number of branches > > * log family can use the --reverse flag Given the number of options available, we have to make some hard decisions about which are worth mentioning in the manual and which can be left to the man pages. The --reverse option doesn't seem important enough to be worth a mention at this point, but I'd listen to reason. The best way to work in --reverse, I think, would be in an examples section as part of a pipeline that needed to get commits in --reverse order. I can't think of one off hand. --b. - 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