From: Pavel Roskin <proski@gnu.org>
Date: Tue, 17 Jan 2006 23:16:02 GMT
Subject: Re: StGIT: "stg new" vs "stg new --force"
Message-ID: <1137539762.12454.11.camel@dv>
In-Reply-To: <20060117215752.GH32585@nowhere.earth>

On Tue, 2006-01-17 at 22:57 +0100, Yann Dirson wrote:
> I commonly also feel the need to "stg refresh" only part of the
> current changes.  Allowing to limit the files to be impacted by a
> refresh could be a good addition.

Absolutely.

> It would even be useful sometimes to dispatch changes to a single file
> into several patches.  When they are distinct enough to be in
> different diff hunks, it is pretty easy to split an existing patch,
> but it could also be useful to only refresh a patch with specific diff
> hunks.  A possibility would be to add a filterdiff-like "-#<n>" flag,
> in addition to the above-suggested "refresh <file>" (and possibly only
> allow to specify a single file together with this flag).

I think if would be better to improve "stg fold" to work on arbitrary
patches.  This way, you prepare the patch in the editor (which would not
be harder than finding hunk numbers) and fold it into the patch of your
choice.  stg should check that the stack remains valid, possibly doing
trivial adjustments to the higher patches.  The current tree should not
be impacted.

-- 
Regards,
Pavel Roskin