All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Konstantin Khomoutov <flatworm@users.sourceforge.net>
Cc: "João Paulo Melo de Sampaio" <jpmelos@gmail.com>,
	"GIT Mailing List" <git@vger.kernel.org>,
	"Jakub Narebski" <jnareb@gmail.com>
Subject: [RFC/PATCH 0/2] Re: Remote branchs -- how can I check them out?
Date: Sun, 30 Jan 2011 15:32:58 -0600	[thread overview]
Message-ID: <20110130213258.GA10039@burratino> (raw)
In-Reply-To: <20110130160556.GI5713@localhost.localdomain>

Konstantin Khomoutov wrote:

> These branches are local to your repository. They are "remote" in the
> sense you're not supposed to modify them directly.
> So to inspect such a branch just use its full name ("origin/next" for
> instance) when working with commands like git-log.
>
> See [1], [2] for more info.
>
> Also your question appears to be quite basic which hints at that you did
> not read a good book on Git before using it.  So starting at [3] is
> recommended -- it mentions a bunch of good books and manuals

Pointing to good references is a valuable thing --- thank you for that.
But I also want to point out that if you need to read a book before Git
becomes usable then we are doing something wrong. :)

In this example, perhaps the "git branch" manual page needs some
improvement?

Jonathan Nieder (2):
  Documentation/branch: split description into subsections
  Documentation/branch: briefly explain what a branch is

 Documentation/git-branch.txt |   62 +++++++++++++++++++++++++-----------------
 1 files changed, 37 insertions(+), 25 deletions(-)

  reply	other threads:[~2011-01-30 21:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-30 15:05 Remote branchs -- how can I check them out? João Paulo Melo de Sampaio
2011-01-30 16:05 ` Konstantin Khomoutov
2011-01-30 21:32   ` Jonathan Nieder [this message]
2011-01-30 21:33     ` [PATCH 1/2] Documentation/branch: split description into subsections Jonathan Nieder
2011-01-31  1:55       ` Sverre Rabbelier
2011-01-30 21:35     ` [PATCH 2/2] Documentation/branch: briefly explain what a branch is Jonathan Nieder
2011-01-31  2:51       ` Junio C Hamano
2011-01-31  0:35     ` [RFC/PATCH 0/2] Re: Remote branchs -- how can I check them out? João Paulo Melo de Sampaio
2011-01-30 16:35 ` Jakub Narebski

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=20110130213258.GA10039@burratino \
    --to=jrnieder@gmail.com \
    --cc=flatworm@users.sourceforge.net \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --cc=jpmelos@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.