From: Matthias Kestenholz <lists@spinlock.ch>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: git@vger.kernel.org
Subject: Re: git pull w/o checkout?
Date: Thu, 22 Jun 2006 15:11:29 +0200 [thread overview]
Message-ID: <20060622131129.GB5134@spinlock.ch> (raw)
In-Reply-To: <E65F8DB5-677B-4C7B-A4EC-5F6FB76D6E9A@kernel.crashing.org>
* Kumar Gala (galak@kernel.crashing.org) wrote:
> I trying to see if there is a way to get the effect of a git-pull w/o
> getting the checked out files.
>
> Any ideas?
Do you want to fetch remote changes without merging them into your
working tree? If you, "git fetch" is your friend.
By the way, pull does the equivalent of a fetch and a subsequent
merge.
Matthias
next prev parent reply other threads:[~2006-06-22 13:11 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
2006-06-22 13:11 ` Matthias Kestenholz [this message]
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=20060622131129.GB5134@spinlock.ch \
--to=lists@spinlock.ch \
--cc=galak@kernel.crashing.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