From: "Bradford Smith" <bradford.carl.smith@gmail.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: git@vger.kernel.org
Subject: Re: user manual wrong about remote branches?
Date: Wed, 11 Jul 2007 11:34:26 -0400 [thread overview]
Message-ID: <f158199e0707110834sdaa29f2x65df784f4b3a6b5e@mail.gmail.com> (raw)
In-Reply-To: <20070711152816.GB4138@fieldses.org>
OK, the problem was the old version of git (1.4.4.2) I used to do the
original clone. Cloning with the latest version gives me what the
manual says I should get.
Thanks!
Bradford C. Smith
On 7/11/07, J. Bruce Fields <bfields@fieldses.org> wrote:
> On Wed, Jul 11, 2007 at 11:21:53AM -0400, Bradford Smith wrote:
> > I got the latest git source like this:
> >
> > git clone git://git.kernel.org/pub/scm/git/git.git
>
> What version of git did you do this first clone with?
>
> > Then I did:
> >
> > make prefix=/usr/local all doc
> > make prefix=/usr/local install install-doc
> >
> > So my current version is:
> >
> > git version 1.5.3.rc0.gbaa79
> >
> > Now, Documentation/user-manual.txt says I should be able to see the
> > remote branch I cloned from when I do this in the source directory.
> >
> > git branch -r
> >
> > However, this command gives no output at all. What gives? Does this
> > mean git-fetch and git-pull won't work properly to keep me up-to-date
> > with the main repository?
>
> The remote branch setup is done on the initial clone. So if you clone
> again with the newly installed version of git, you'll probably see
> what's expected.
>
> --b.
>
prev parent reply other threads:[~2007-07-11 15:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-11 15:21 user manual wrong about remote branches? Bradford Smith
2007-07-11 15:28 ` J. Bruce Fields
2007-07-11 15:34 ` Bradford Smith [this message]
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=f158199e0707110834sdaa29f2x65df784f4b3a6b5e@mail.gmail.com \
--to=bradford.carl.smith@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).