git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Carlos Rica" <jasampler@gmail.com>
To: "J. Bruce Fields" <bfields@fieldses.org>, git@vger.kernel.org
Subject: Little fix and suggestion for the git tutorial
Date: Thu, 21 Jun 2007 18:45:01 +0200	[thread overview]
Message-ID: <1b46aba20706210945h49139cc2y69d2de972f014189@mail.gmail.com> (raw)

Sorry for not sending a patch, I was following the tutorial and found
this, in the section "Using git for collaboration":

 307 With this, you can perform the first operation alone using the
 308 "git fetch" command without merging them with her own branch,
 309 using:

I think that "you" should be replaced with "she".

I have a suggestion also that I don't know how to fix. The text in
that section seems to say something like you need to add a "remote"
alias to be able to run fetch for retrieving without merging:

...[remote add <alias>]...

 307 With this, you can perform the first operation alone using the
 308 "git fetch" command without merging them with her own branch,
 309 using:

....[fetch <alias>]...

 315 Unlike the longhand form, when Alice fetches from Bob using a
 316 remote repository shorthand set up with `git remote`, what was
 317 fetched is stored in a remote tracking branch, in this case
 318 `bob/master`.  So after this:

I'm not sure, but I think that you could use fetch without the need of
an alias. I think that here it is trying to avoid more advanced
explanations or longer commands, however I don't know how to say it
better, perhaps mentioning that this way it is easier, without
omitting that it could be done without a "remote" alias for the repo.

That's all, thank you

             reply	other threads:[~2007-06-21 16:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-21 16:45 Carlos Rica [this message]
2007-06-22  3:18 ` Little fix and suggestion for the git tutorial J. Bruce Fields

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=1b46aba20706210945h49139cc2y69d2de972f014189@mail.gmail.com \
    --to=jasampler@gmail.com \
    --cc=bfields@fieldses.org \
    --cc=git@vger.kernel.org \
    /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).