GNU bug report logs - #78216
[PATCH] * admin/MAINTAINERS: Added myself as the vtable.el maintainer.

Previous Next

Full log

Message #17 received at 78216 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Stéphane Marks <shipmints <at> gmail.com>
Cc: corwin <at> bru.st, 78216 <at> debbugs.gnu.org
Subject: Re: bug#78216: [PATCH] * admin/MAINTAINERS: Added myself as the
 vtable.el maintainer.
Date: Thu, 19 Jun 2025 08:09:02 +0300

> Cc: 78216 <at> debbugs.gnu.org
> From: Stéphane Marks <shipmints <at> gmail.com>
> Date: Wed, 18 Jun 2025 13:02:24 -0400
> 
> My aim will be to create a feature branch for the vtable fixes and updates (of which there are quite a few
> along with improved documentation) with the ultimate goal to merge it to master.

A feature branch is justified when you are working on a large feature
that might potentially break the existing features on master.  Is that
the case?  If you intend to install a significant number of changes,
but each one of them will be pushed as a single changeset and will not
cause vtable to be in inconsistent state that makes it unfit for
everyday usage, then we prefer to install such changes on master.
This has two important advantages: (1) it lets more people test the
changes (since the number of people who will checkout such a branch is
expected to be small), and (2) it is easier to install such changes
because that avoids the need to switch branches, especially if someone
else will install your patches.

Thanks.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.