From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin-apps@cygwin.com
Cc: Jon Turney <jon.turney@dronecode.org.uk>
Subject: [PATCH rebase 0/2] Avoid unncessary rebases
Date: Fri, 09 Feb 2018 12:00:00 -0000 [thread overview]
Message-ID: <20180209115941.512448-1-jon.turney@dronecode.org.uk> (raw)
Add some dignostics which report why a rebase is taking place.
Use that information to fix some errors causing unnecessary rebases
In those cases, we were often rebasing a DLL to the same address, so we could
also drop the rebase if the base address isn't actually changing, but we don't
seme to keep around the infomation to do that, currently.
Jon Turney (2):
Make verbose give a reason why a rebase is needed
Fix some errors which cause unnecessary rebases
rebase.c | 59 ++++++++++++++++++++++++++++++++++++++++++++++-------------
1 file changed, 46 insertions(+), 13 deletions(-)
--
2.16.1
next reply other threads:[~2018-02-09 12:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-09 12:00 Jon Turney [this message]
2018-02-09 12:01 ` [PATCH 1/2] Make verbose give a reason why a rebase is needed Jon Turney
2018-02-09 20:02 ` Corinna Vinschen
2018-02-09 12:01 ` [PATCH 2/2] Fix some errors which cause unnecessary rebases Jon Turney
2018-02-09 19:52 ` Corinna Vinschen
2018-02-13 12:48 ` [PATCH rebase 0/2] Avoid unncessary rebases Jon Turney
2018-02-13 18:32 ` Achim Gratz
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=20180209115941.512448-1-jon.turney@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-apps@cygwin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).