All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: "Santi Béjar" <sbejar@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] user-manual.txt: Some doc updates
Date: Thu, 19 Apr 2007 12:02:35 -0400	[thread overview]
Message-ID: <20070419160235.GE9101@fieldses.org> (raw)
In-Reply-To: <87hcrcjre3.fsf@gmail.com>

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.

  reply	other threads:[~2007-04-19 16:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-19 15:49 [PATCH] user-manual.txt: Some doc updates Santi Béjar
2007-04-19 16:02 ` J. Bruce Fields [this message]
2007-04-19 16:07   ` Nicolas Pitre
2007-04-19 17:01     ` J. Bruce Fields
2007-04-19 19:51       ` Santi Béjar
2007-05-08  3:21 ` J. Bruce Fields
2007-05-08  8:37   ` Santi Béjar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070419160235.GE9101@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=git@vger.kernel.org \
    --cc=sbejar@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.