From: Philip Oakley <philipoakley@iee.org>
To: GitList <git@vger.kernel.org>
Subject: [RFC/PATCH 2/2] Doc rebase: describe the priority of published work
Date: Sun, 19 May 2013 12:52:09 +0100 [thread overview]
Message-ID: <1368964329-1600-3-git-send-email-philipoakley@iee.org> (raw)
In-Reply-To: <1368964329-1600-1-git-send-email-philipoakley@iee.org>
Give details of the implied priority in the description section.
Signed-off-by: Philip Oakley <philipoakley@iee.org>
---
wording based on:
http://article.gmane.org/gmane.comp.version-control.git/222581
http://article.gmane.org/gmane.comp.version-control.git/223816
http://article.gmane.org/gmane.comp.version-control.git/217410
http://article.gmane.org/gmane.comp.version-control.git/222763
---
Documentation/git-rebase.txt | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/Documentation/git-rebase.txt b/Documentation/git-rebase.txt
index 87a8095..24d16ef 100644
--- a/Documentation/git-rebase.txt
+++ b/Documentation/git-rebase.txt
@@ -20,6 +20,12 @@ DESCRIPTION
by default, to the head of the branch's upstream, or onto a new base
if given.
+In its minimal form, having built locally on the (current) branch,
+use `git rebase` to catch up with its published upstream state to
+create a new linear history. Importantly, `git rebase` is a way to
+replay your work on top of the work of others. It is not about
+integrating other people's changes into your work.
+
If <branch> is specified, 'git rebase' will perform an automatic
`git checkout <branch>` before doing anything else. Otherwise
it remains on the current branch.
--
1.8.1.msysgit.1
prev parent reply other threads:[~2013-05-19 11:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-19 11:52 [RFC/PATCH 0/2] Improve rebase documenation Philip Oakley
2013-05-19 11:52 ` [RFC/PATCH 1/2] Doc rebase: Describe rebase as excluding merge commits Philip Oakley
2013-05-19 18:08 ` Jonathan Nieder
2013-05-19 22:41 ` Philip Oakley
2013-05-20 4:43 ` Junio C Hamano
2013-05-20 21:55 ` Philip Oakley
2013-05-20 22:29 ` Junio C Hamano
2013-05-19 11:52 ` Philip Oakley [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=1368964329-1600-3-git-send-email-philipoakley@iee.org \
--to=philipoakley@iee.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).