From: Joshua N Pritikin <jpritikin@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: interactive rebase should better highlight the not-applying commit
Date: Wed, 12 Oct 2016 13:02:07 -0400 [thread overview]
Message-ID: <20161012170207.lapdv5h5aws4k4pw@droplet> (raw)
In-Reply-To: <alpine.DEB.2.20.1610121815160.197091@virtualbox>
On Wed, Oct 12, 2016 at 06:24:37PM +0200, Johannes Schindelin wrote:
> No, a false belief in your own shortcomings, as you thought it would be
> easier to address your wishes for somebody else than you.
Ah, shucks, I guess I could jump in.
> But maybe I read it all wrong and you do want to make this happen
> yourself, and you simply want a little advice how to go about it?
Ugh, if you insist. You really know how to hold someone's feet to the
fire, eh?
> > On Tue, Oct 11, 2016 at 02:25:19PM -0700, Stefan Beller wrote:
> > > On Tue, Oct 11, 2016 at 12:07 PM, Joshua N Pritikin <jpritikin@pobox.com> wrote:
> > > However IIUC currently rebase is completely rewritten/ported to C
> > > where it is easier to add color support as we do have some color
> > > support in there already.
> >
> > Sounds great. Is there a beta release that I can try out?
>
> There is no release as such, unless you count Git for Windows v2.10.0.
Nope, that doesn't count. ;-)
> But you can try the `interactive-rebase` branch of
> https://github.com/dscho/git; please note, though, that my main aim was to
> be as faithful as possible in the conversion (modulo speed, of course).
Hm OK
> > Sometimes I do a rebase to fix some tiny thing 10-15 commits from HEAD.
> > Maybe only 1 file is affected and there are no merge conflicts, but when
> > rebase reapplies all the commits, the timestamps of lots of unmodified
> > files change even though they are unmodified compared to before the
> > rebase.
>
> Well, they *were* modified, right?
Were they? Isn't that just an artefact of the implementation?
> A workaround would be to create a new worktree using the awesome `git
> worktree` command, perform the rebase there (on an unnamed branch -- AKA
> "detached HEAD", no relation to Helloween), and then come back to the
> original worktree and reset --hard to the new revision. That reset would
> detect that there are actually no changes required to said files.
What would be the problem with doing this by default? Or could it be a
configuration option that can be enabled?
--
Joshua N. Pritikin, Ph.D.
Virginia Institute for Psychiatric and Behavioral Genetics
Virginia Commonwealth University
PO Box 980126
800 E Leigh St, Biotech One, Suite 1-133
Richmond, VA 23219
http://people.virginia.edu/~jnp3bc
next prev parent reply other threads:[~2016-10-12 17:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-11 19:07 interactive rebase should better highlight the not-applying commit Joshua N Pritikin
2016-10-11 20:55 ` Stefan Beller
2016-10-12 16:14 ` Johannes Schindelin
2016-10-11 21:25 ` Stefan Beller
2016-10-12 13:27 ` Joshua N Pritikin
2016-10-12 16:24 ` Johannes Schindelin
2016-10-12 17:02 ` Joshua N Pritikin [this message]
2016-10-13 10:40 ` Johannes Schindelin
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=20161012170207.lapdv5h5aws4k4pw@droplet \
--to=jpritikin@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--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).