From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: git pull w/o checkout?
Date: Thu, 22 Jun 2006 15:32:31 +0200 [thread overview]
Message-ID: <e7e65f$dhf$1@sea.gmane.org> (raw)
In-Reply-To: A4C01915-3337-460C-BE19-7AC17249BE50@kernel.crashing.org
Kumar Gala wrote:
>
> On Jun 22, 2006, at 8:13 AM, Jeff King wrote:
>
>> On Thu, Jun 22, 2006 at 08:10:10AM -0500, Kumar Gala wrote:
>>
>>>> git-fetch?
>>> Its the first half, still need to resolve FETCH_HEAD, HEAD, etc..
>>
>> Can you elaborate on what you're trying to accomplish?
>
> A local mirror of a git tree. I can do the clone easy enough, its
> trying to figure out the updates after the fact that is the issue.
Assuming typical configuration, with the following in remotes/origin
---[ <path-to-repo>/.git/remotes/origin ]----
URL: git://git.kernel.org/pub/scm/git/git.git
Pull: refs/heads/master:refs/heads/origin
Pull:+refs/heads/pu:refs/heads/pu
Pull: refs/heads/man:refs/heads/man
Pull: refs/heads/html:refs/heads/html
Pull: refs/heads/next:refs/heads/next
Pull: refs/heads/todo:refs/heads/todo
Pull: refs/heads/maint:refs/heads/maint
---------------------------------------------
to update your repository, do:
$ git checkout master
$ git fetch origin
Any branch except listed ot fhose fetched to will do, or even any command
that leaves HEAD different than one of the branches fetched to. Everything
is updated. Then you can do the second part of pull, using
$ git checkout master
$ git pull . master
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2006-06-22 13:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-22 12:51 git pull w/o checkout? Kumar Gala
2006-06-22 13:05 ` Jeff King
2006-06-22 13:10 ` Kumar Gala
2006-06-22 13:13 ` Jeff King
2006-06-22 13:15 ` Kumar Gala
2006-06-22 13:32 ` Jakub Narebski [this message]
2006-06-22 13:11 ` Matthias Kestenholz
2006-06-22 13:13 ` Kumar Gala
2006-06-22 13:17 ` Jeff King
2006-06-22 13:20 ` Kumar Gala
2006-06-22 13:25 ` Jeff King
2006-06-22 13:34 ` Mathieu Chouquet-Stringer
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='e7e65f$dhf$1@sea.gmane.org' \
--to=jnareb@gmail.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