From: garyc618 <gary.carter@eigen.com>
To: git@vger.kernel.org
Subject: How to make fetch get everything?
Date: Tue, 31 May 2011 17:06:16 -0700 (PDT) [thread overview]
Message-ID: <1306886776234-6425155.post@n2.nabble.com> (raw)
Hi List,
In one book it says that "git fetch [remote]" pulls down everything you
don't currently have in your local repository. However, when I look at
FETCH_HEAD it only has the master head. Other branches don't seem to get
fetched.
I tried "git fetch [remote] *:*" but that gave fatal error messages.
Then I tried "git fetch [remote] "*:foo/*" which worked great - I got every
single branch.
I am setting up a shared repo for a small devel team, which I want everyone
to push/pull to. It seems safer to do that, than to have people just make
the shared mount their current directory, then run git commands, but how can
people see every branch in the shared repo using only fetch, other than the
trick with foo/* that I used above? Am I missing something, or is this just
going to be kind of clunky?
Thanks,
Gary Carter
--
View this message in context: http://git.661346.n2.nabble.com/How-to-make-fetch-get-everything-tp6425155p6425155.html
Sent from the git mailing list archive at Nabble.com.
next reply other threads:[~2011-06-01 0:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-01 0:06 garyc618 [this message]
2011-06-01 6:59 ` How to make fetch get everything? Johannes Sixt
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=1306886776234-6425155.post@n2.nabble.com \
--to=gary.carter@eigen.com \
--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).