[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Gnus overrides.texi and WEBHACKDEVEL

From: Ted Zlatanov
Subject: Re: Gnus overrides.texi and WEBHACKDEVEL
Date: Sat, 05 Feb 2011 10:01:46 -0600
User-agent: Gnus/5.110011 (No Gnus v0.11) Emacs/24.0.50 (gnu/linux)

On Sat, 05 Feb 2011 17:39:33 +0200 Eli Zaretskii <address@hidden> wrote: 

>> From: Ted Zlatanov <address@hidden>
>> Date: Sat, 05 Feb 2011 09:18:37 -0600
>> Cc: address@hidden
EZ> More generally, what is a user supposed to do if she does want to put
EZ> something on gnus-overrides.texi?  That's a versioned file, so "bzr
EZ> status" will show it as modified, and there's still a danger of having
EZ> it committed inadvertently.  How is this better than just modifying
EZ> gnu.texi or any other file directly?
>> The user wouldn't touch them, they are for the developers.

EZ> By "user" I _did_ mean developers in this case.  How do we prevent the
EZ> danger of committing a modified file?  Versioned files that are
EZ> modified are generally meant to be committed at some point.

I see what you mean.  I want to use it differently, not for temporary
modifications but for regular use.  If it's modified, it should be
committed by the developer.  It's supposed to be in the VCS and
unchanging regardless of the make actions taken by the user.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]