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: Mon, 7 May 2007 23:21:15 -0400 [thread overview]
Message-ID: <20070508032115.GC9471@fieldses.org> (raw)
In-Reply-To: <87hcrcjre3.fsf@gmail.com>
On Thu, Apr 19, 2007 at 05:49:40PM +0200, Santi Béjar wrote:
> git branch::
> + list all local branches
> +git branch -r::
> + list all remote branches
> +git branch -a::
> list all branches
I think I dropped this just because "remote branches" haven't yet been
introduced at this point in the manual. (That's not till "Examining
branches from a remote repository".) Could be some sections should be
reordered--suggestions welcomed.
> +-------------------------------------------------
> +$ git diff HEAD
> +-------------------------------------------------
> +
> +shows the difference between the working tree and HEAD.
> +
I took the mention of this later on, but didn't think it was necessary
to mention here too.
> @@ -1872,10 +1880,7 @@ As with git-fetch, you may also set up configuration options to
> save typing; so, for example, after
>
> -------------------------------------------------
> -$ cat >.git/config <<EOF
> -[remote "public-repo"]
> - url = ssh://yourserver.com/~you/proj.git
> -EOF
> +$ git config remote."public-repo".url ssh://yourserver.com/~you/proj.git
> -------------------------------------------------
I think this was adequately discussed.
> +You can also instantly browse your working repository in gitweb using:
> +
> +-------------------------------------------------
> +$ git instaweb
> +-------------------------------------------------
> +
> +See gitlink:git-instaweb[1] for details.
> +
That's nifty, but doesn't seem necessary at this point, and doesn't
quite fit in the section (which is about public repositories).
Others look good, thanks.
But if you want whole patches applied or rejected with explanation, I
think you may have to be prepared to revise and resubmit when there are
objections to parts.
--b.
next prev parent reply other threads:[~2007-05-08 3:21 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
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 [this message]
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=20070508032115.GC9471@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).