Re: [PATCH 1/4] git-prompt.sh: add submodule indicator

From: Stefan Beller <sbeller@google.com>
Date: Feb 6, 2017, 10:13 UTC
Message-ID: <CAGZ79kZyofKoAzFH7zU7DDndRPbiS1L+7d7Y6HqRZ+_4JoJ_zw@mail.gmail.com>
In-Reply-To: <CA+P7+xp0QJZkiYzgBhPvYPsG7iqRDhRQUjcdgf_GHU-93bSO-g@mail.gmail.com>

On Sun, Feb 5, 2017 at 9:55 PM, Jacob Keller <jacob.keller@gmail.com> wrote:

Show 17 quoted lines

> On Sun, Feb 5, 2017 at 8:23 PM, Stefan Beller <sbeller@google.com> wrote:
>>
>> (unrelated side note:)
>> At GitMerge facebook presented their improvements on mercurial
>> and one of the things was "hg absorb". It would take the dirty hunks/lines
>> of the working tree and amend them into the "stack of commits", i.e. into
>> your local unpublished history. So instead of making fixup commits
>> and doing the whole interactive rebase thing, it would do it automatically
>> for you. I think that is a neat time saver.
>>
>> Thanks,
>> Stefan
>
> How exactly was it different from doing "git  commit --fixup xyz" and
> "git rebase -i --autosquash"? Like, what was the advantage to the user
> facing workflow? Just curious to see if we could learn something from
> it.

My impression is that all local changes were split up and the "xyz" was determined based off a heuristic, e.g. blame(?) and then the rebase is run automatically after that, i.e. having just one command for a complete workflow here, moving up a whole level in abstraction.