Re: [PATCH] m4sh: always re-exec with $CONFIG_SHELL, if it's set

[Paul Eggert]

On 11/08/11 11:54, Stefano Lattarini wrote:
>> I'd rather avoid a branch if I could,
>> >
> Why?  That is the best way to keep the work public and going, without 
> risking to destabilize the code base.

My experience with branches in Emacs (a much more-heavily-maintained
project) is that their advantages in stability are often outweighed by
their disadvantages in maintenance overhead.  There's no real problem
if a branch is used by just one developer (as this is logically equivalent
to a private copy), nor if a set of developers works exclusively in a
branch (this is rarer, but it can work), but there is a real hassle
if stuff needs to be shared among branches.

In this particular case, if you want to create a branch that (presumably)
just you will use, and you're doing it to publish your work, that'd be OK.
(Maybe you can take over the 'experimental' branch, which
hasn't been used since 1999....)

One thing that'd be helpful is to put the four issues mentioned in your previous
message into the branch somewhere, so that other developers are reminded
of pending problems.

And thanks for looking into the problem, by the way!