GNU bug report logs - #79346
igc: PolicyShouldCollectWorld

Previous Next

Full log

View this message in rfc822 format

From: Gerd Möllmann <gerd.moellmann <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 79346 <at> debbugs.gnu.org, eller.helmut <at> gmail.com
Subject: bug#79346: igc: PolicyShouldCollectWorld
Date: Sat, 06 Sep 2025 09:48:34 +0200

Eli Zaretskii <eliz <at> gnu.org> writes:

SW>> From: Gerd Möllmann <gerd.moellmann <at> gmail.com>
>> Cc: eller.helmut <at> gmail.com,  79346 <at> debbugs.gnu.org
>> Date: Sat, 06 Sep 2025 09:02:21 +0200
>> 
>> Eli Zaretskii <eliz <at> gnu.org> writes:
>> 
>> >> From: Gerd Möllmann <gerd.moellmann <at> gmail.com>
>> >> Cc: Eli Zaretskii <eliz <at> gnu.org>,  79346 <at> debbugs.gnu.org
>> >> Date: Fri, 05 Sep 2025 20:05:26 +0200
>> >> 
>> >> I've branched a new scratch/igc2 from feature/igc for more "freestyle"
>> >> changes.
>> >
>> > Will someone merge from that branch to feature/igc?  Or is this a
>> > completely independent effort?
>> >
>> > IOW, what is the intended use of this new branch, and how, if at all
>> > will it fit into the work on adding igc to Emacs?
>> >
>> > For example, if I have an igc-related change to install, on which of
>> > the two branches should I do that?
>> 
>> ATM, it's thought of a place where one can experiment with things
>> without being faced with bureaucratic hurdles, so to speak. Depends on
>> whether Helmut finds that useful, otherwise I'd delete it again.
>
> What "bureaucratic hurdles" are those?

A feature branch has some rules to follow, I'd guess. 

>
> Also, does this mean this branch is only for Helmut (and maybe
> yourself) to use, and others should not push anything there without
> talking to you first?

Yes.

> And my question about merges still stands, in case this branch will
> get some changes.

No automatic merges from there to feature/igc. 

Previous Next

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