This is the mail archive of the
mailing list for the Cygwin project.
Re: [rebase PATCH] Introduce --no-rebase flag
- From: Michael Haubenwallner <michael dot haubenwallner at ssi-schaefer dot com>
- To: cygwin-patches at cygwin dot com
- Date: Wed, 24 Apr 2019 15:08:25 +0200
- Subject: Re: [rebase PATCH] Introduce --no-rebase flag
- References: <firstname.lastname@example.org> <87bm1axsls.fsf@Rainer.invalid>
On 4/13/19 9:38 AM, Achim Gratz wrote:
> Michael Haubenwallner writes:
>> The --no-rebase flag is to update the database for new files, without
>> performing a rebase. The file names provided should have been rebased
>> using the --oblivious flag just before.
> That name is somewhat strange, how about "--enlist"?
>From my point of view, rebase does perform multiple steps,
each being enabled by default, but each to become optional:
1) Perform the "rebase", with flag for disabling to be defined.
2) "Record" (or "enlist") to database, with --oblivious flag for disabling.
While it is fine to have both enabled by default, disabling one step by
explicitly enabling the (already enabled) other step feels confusing...
So, consequently, what about renaming --oblivious to --no-record (or --no-enlist),
to end up with the "rebase" and the "record" (or "enlist") steps both being
disabled by the according --no-<step> flag?