From: Rob Browning <rlb@defaultvalue.org>
To: Andreas Schwab <schwab@linux-m68k.org>,
Lars Magne Ingebrigtsen <larsi@gnus.org>
Cc: David Kastrup <dak@gnu.org>, emacs-devel@gnu.org
Subject: Re: Cluttering the git tree
Date: Thu, 20 Nov 2014 00:18:36 -0600 [thread overview]
Message-ID: <87oas2z96r.fsf@trouble.defaultvalue.org> (raw)
In-Reply-To: <87wq6tzafy.fsf@igel.home>
Andreas Schwab <schwab@linux-m68k.org> writes:
> Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
>> Well, he could just say "git pull --rebase", right?
>
> That doesn't clean up the intermediate commits, it just transplants
> them.
And in more detail, it effectively
1) runs git fetch to update the local copy of the relevant upstream
branch,
2) removes all of your pending commits from the current branch,
3) moves the current branch forward to match the local upstream copy
that was just fetched,
4) and then attempts to reapply all of the patches that were removed
in step 2 to the updated current branch (i.e. the rebase).
If anything goes wrong with a patch in step 4, you'll be walked through
a resolution process (as with all rebases). And at any point, if you
want to start over, you can run "git rebase --abort".
Hope this helps
--
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
next prev parent reply other threads:[~2014-11-20 6:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-17 20:51 Cluttering the git tree Ulf Jasper
2014-11-17 22:36 ` David Kastrup
2014-11-17 22:53 ` Lars Magne Ingebrigtsen
2014-11-17 23:14 ` Andreas Schwab
2014-11-20 6:18 ` Rob Browning [this message]
2014-11-20 5:03 ` Bill Wohler
2014-11-20 17:42 ` Ulf Jasper
2014-11-20 18:27 ` Achim Gratz
2014-11-20 19:01 ` Ulf Jasper
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=87oas2z96r.fsf@trouble.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=dak@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=schwab@linux-m68k.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.