From: Taylor Blau <me@ttaylorr.com>
To: Stefan Xenos <sxenos@google.com>
Cc: git@vger.kernel.org
Subject: Re: Git Evolve
Date: Mon, 1 Oct 2018 18:23:26 -0700 [thread overview]
Message-ID: <20181002012326.GA96979@syl> (raw)
In-Reply-To: <CAPL8ZivFmHqS2y+WmNR6faRMnuahiqwPVYsV99NiJ1QLHOs9fQ@mail.gmail.com>
Hi Stefan,
On Sat, Sep 29, 2018 at 04:00:04PM -0700, Stefan Xenos wrote:
> Hello, List!
>
> I'm interested in porting something like Mercurial's evolve command to
> Git.
Welcome to Git :-). I think that the discussion in this thread is good,
but it's not why I'm replying. I have also wanted a Mercurial feature in
Git, but a different one than yours.
Specifically, I've wanted the 'hg absorb' command. My understanding of
the commands functionality is that it builds a sort of flamegraph-esque
view of the blame, and then cascades downwards parts of a change. I am
sure that I'm not doing the command justice, so I'll defer to [1] where
it is explained in more detail.
The benefit of this command is that it gives you a way to--without
ambiguity--absorb changes into earlier commits, and in fact, the
earliest commit that they make sense to belong to.
This would simplify my workflow greatly when re-rolling patches, as I
often want to rewrite a part of an earlier commit. This is certainly
possible by a number of different `git rebase` invocations (e.g., (1)
create fixup commits, and then re-order them, or (2) mark points in your
history as 'edit', and rewrite them in a detached state, and I'm sure
many more).
I'm curious if you or anyone else has thought about how this might work
in Git.
Thanks,
Taylor
[1]: http://files.lihdd.net/hgabsorb-note.pdf
next prev parent reply other threads:[~2018-10-02 1:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-29 23:00 Git Evolve Stefan Xenos
2018-09-30 0:55 ` Junio C Hamano
2018-09-30 20:17 ` Stefan Xenos
2018-10-04 16:05 ` Jakub Narebski
2018-10-04 17:29 ` Stefan Xenos
2018-10-01 12:37 ` Derrick Stolee
2018-10-31 21:12 ` Stefan Xenos
2018-10-02 1:23 ` Taylor Blau [this message]
2018-10-02 9:11 ` Ævar Arnfjörð Bjarmason
2018-10-02 19:35 ` Stefan Xenos
2018-10-02 22:25 ` Kyle Meyer
2018-10-02 23:09 ` Taylor Blau
2018-11-09 13:06 ` 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=20181002012326.GA96979@syl \
--to=me@ttaylorr.com \
--cc=git@vger.kernel.org \
--cc=sxenos@google.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 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.