Re: StGIT: "stg new" vs "stg new --force"

From: Yann Dirson <ydirson@altern.org>
Date: Jan 18, 2006, 19:37 UTC
Message-ID: <20060118193717.GI32585@nowhere.earth>
In-Reply-To: <1137539762.12454.11.camel@dv>

On Tue, Jan 17, 2006 at 06:16:02PM -0500, Pavel Roskin wrote:

Show 14 quoted lines

> > 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.

This sounds like a good idea as well (and I would use it on a near daily basis as well ;). Obviously such a request can also fail, eg. when requesting to fold a change into a patch, where a subsequent patch modifies the same lines.

But it would not be a replacement to selecting changes with a granularity finer than file-level, which is what I wanted to suggest.

Best regards,

-- 
Yann Dirson    <ydirson@altern.org> |
Debian-related: <dirson@debian.org> |   Support Debian GNU/Linux:
                                    |  Freedom, Power, Stability, Gratis
     http://ydirson.free.fr/        | Check <http://www.debian.org/>