Re: [PATCH 1/8] sequencer: introduce new commands to reset the revision

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Jan 18, 2018, 21:13 UTC
Message-ID: <nycvar.QRO.7.76.6.1801182212210.31@ZVAVAG-6OXH6DA.rhebcr.pbec.zvpebfbsg.pbz>
In-Reply-To: <CA+P7+xozcQD2xuys6mh8MsfcYZ_nb2c9yxhDxkc7FTN2SfoofQ@mail.gmail.com>

Hi Jake,

On Thu, 18 Jan 2018, Jacob Keller wrote:

Show 19 quoted lines

> On Thu, Jan 18, 2018 at 7:35 AM, Johannes Schindelin
> <johannes.schindelin@gmx.de> wrote:
> > This commit implements the commands to label, and to reset to, given
> > revisions. The syntax is:
> >
> >         label <name>
> >         reset <name>
> >
> > As a convenience shortcut, also to improve readability of the generated
> > todo list, a third command is introduced: bud. It simply resets to the
> > "onto" revision, i.e. the commit onto which we currently rebase.
> >
> 
> The code looks good, but I'm a little wary of adding bud which
> hard-codes a specific label. I suppose it does grant a bit of
> readability to the resulting script... ? It doesn't seem that
> important compared to use using "reset onto"? At least when
> documenting this it should be made clear that the "onto" label is
> special.

Indeed, `bud` helped me more in the earlier times of the Git garden shears when I had to *introduce* branch structure into the long list of Git for Windows' patches.

If there are no voices in favor of `bud` other than mine, I will remove support for it in the next iteration.

Ciao, Dscho