From: Daniel Barkalow <barkalow@iabervon.org>
To: git@vger.kernel.org
Subject: [PATCH] Note that '.' is a useful value for <repository> in git-pull.
Date: Mon, 31 Oct 2005 22:28:16 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.64.0510312220230.25300@iabervon.org> (raw)
Mention in the tutorial and in the documentation for git-pull that you can
merge local branches with all the bells and whistles with
"git pull . <branch>"
Signed-off-by: Daniel Barkalow <barkalow@iabervon.org>
---
"git pull . <branch>" does, in fact, do exactly what I wanted, and, when
the tutorial mentioned that you could do this, it didn't mention why you
might want to.
Documentation/git-pull.txt | 3 ++-
Documentation/tutorial.txt | 12 ++++++++++--
2 files changed, 12 insertions(+), 3 deletions(-)
applies-to: 8c8ace55eb085e930dcc9482f7cf66f9399374b4
0ba51e8c8298aff4256bd63289071f23b4d83db3
diff --git a/Documentation/git-pull.txt b/Documentation/git-pull.txt
index bae05de..fe0c18a 100644
--- a/Documentation/git-pull.txt
+++ b/Documentation/git-pull.txt
@@ -13,7 +13,8 @@ SYNOPSIS
DESCRIPTION
-----------
-Runs 'git-fetch' with the given parameters.
+Runs 'git-fetch' with the given parameters. This is effectively
+skipped if the repository is '.'
When only one ref is downloaded, runs 'git resolve' to merge it
into the local HEAD. Otherwise uses 'git octopus' to merge them
diff --git a/Documentation/tutorial.txt b/Documentation/tutorial.txt
index b9f737e..78443a9 100644
--- a/Documentation/tutorial.txt
+++ b/Documentation/tutorial.txt
@@ -1027,8 +1027,16 @@ course, you will pay the price of more d
multiple working trees, but disk space is cheap these days.
[NOTE]
-You could even pull from your own repository by
-giving '.' as <remote-repository> parameter to `git pull`.
+
+One useful special case is
+
+ git pull . <branch-name>
+
+which does about the same thing as the `git resolve` calls for merging
+local branches, except that you don't have to type in the message or
+the side you're merging into (which is the branch that you have
+checked out).
+
It is likely that you will be pulling from the same remote
repository from time to time. As a short hand, you can store
---
0.99.8.GIT
reply other threads:[~2005-11-01 3:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Pine.LNX.4.64.0510312220230.25300@iabervon.org \
--to=barkalow@iabervon.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