From: martinvz <martin.von.zweigbergk@gmail.com>
To: git@vger.kernel.org
Subject: Re: Difference between pull --rebase and fetch+rebase
Date: Fri, 8 Jan 2010 11:41:16 -0800 (PST) [thread overview]
Message-ID: <1262979676402-4274470.post@n2.nabble.com> (raw)
In-Reply-To: <adf1fd3d1001080305k138a2670k17a126cc0b8430b8@mail.gmail.com>
Santi Béjar-2 wrote:
>
> Yes, it is. The code expects that you always branch your topic
> branches from the upstream branch, so all the possible fork points are
> in the reflog. Your flow was to create the topic from a local commit
> and then push that commit.
>
Thanks, Santi! After thinking for a while about what you said, I think I
understand. That could definitely be what I did, although I can't remember
for sure.
Would it make sense to teach "git rebase" the same tricks as "git pull
--rebase"?
Santi Béjar-2 wrote:
>
> By the way, when Git tries to apply these two commits it should detect
> that they are already applied so it should do nothing, isn't it?
>
Almost - it fails, but the merge tool resolves it automatically.
Martin
--
View this message in context: http://n2.nabble.com/Difference-between-pull-rebase-and-fetch-rebase-tp4266164p4274470.html
Sent from the git mailing list archive at Nabble.com.
prev parent reply other threads:[~2010-01-08 19:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-07 12:23 Difference between pull --rebase and fetch+rebase martinvz
2010-01-07 12:58 ` martinvz
2010-01-07 16:00 ` Santi Béjar
2010-01-07 18:44 ` martinvz
2010-01-07 22:33 ` Santi Béjar
2010-01-07 23:38 ` martinvz
2010-01-08 11:05 ` Santi Béjar
2010-01-08 19:41 ` martinvz [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=1262979676402-4274470.post@n2.nabble.com \
--to=martin.von.zweigbergk@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;
as well as URLs for NNTP newsgroup(s).