From: Elijah Newren <newren@gmail.com>
To: git@vger.kernel.org
Cc: "Santi Béjar" <santi@agolina.net>,
gitster@pobox.com, "Elijah Newren" <newren@gmail.com>
Subject: [PATCH 0/2] Fix spurious conflicts with pull --rebase
Date: Fri, 6 Aug 2010 08:05:01 -0600 [thread overview]
Message-ID: <1281103503-27515-1-git-send-email-newren@gmail.com> (raw)
This patch series fixes git pull --rebase failing to detect if "local"
patches are already upstream in cases where the upstream repository is
not itself rebased. Also in the non-rebased upstream case, this
series avoids checking/applying more patches than needed (i.e. avoids
having rebase work on commits which are already reachable from
upstream).
It would be nice to make 'git pull --rebase' able to detect if patches
being applied are already part of upstream in cases where the upstream
repository has been rebased. As far as I can tell, that would require
changes to format-patch to allow it to be told what 'upstream' is, and
some changes to git-pull.sh/git-rebase.sh to pass it this information.
Elijah Newren (2):
t5520-pull: Add testcases showing spurious conflicts from git pull
--rebase
pull --rebase: Avoid spurious conflicts and reapplying unnecessary
patches
git-pull.sh | 34 ++++++++++++++++++++-----------
t/t5520-pull.sh | 59 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
2 files changed, 81 insertions(+), 12 deletions(-)
next reply other threads:[~2010-08-06 14:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-06 14:05 Elijah Newren [this message]
2010-08-06 14:05 ` [PATCH 1/2] t5520-pull: Add testcases showing spurious conflicts from git pull --rebase Elijah Newren
2010-08-06 14:05 ` [PATCH 2/2] pull --rebase: Avoid spurious conflicts and reapplying unnecessary patches Elijah Newren
2010-08-08 19:27 ` [PATCH 0/2] Fix spurious conflicts with pull --rebase Elijah Newren
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=1281103503-27515-1-git-send-email-newren@gmail.com \
--to=newren@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=santi@agolina.net \
/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).