Re: [PATCH] user-manual.txt: Some doc updates

> 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.