From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Cc: ding@gnus.org
Subject: Re: Gnus overrides.texi and WEBHACKDEVEL
Date: Sat, 05 Feb 2011 10:01:46 -0600 [thread overview]
Message-ID: <87y65ua2s5.fsf@lifelogs.com> (raw)
In-Reply-To: <83wrle8p8q.fsf@gnu.org>
On Sat, 05 Feb 2011 17:39:33 +0200 Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Ted Zlatanov <tzz@lifelogs.com>
>> Date: Sat, 05 Feb 2011 09:18:37 -0600
>> Cc: ding@gnus.org
>>
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.
Ted
next prev parent reply other threads:[~2011-02-05 16:01 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-05 9:35 Revision 103117 on the Emacs trunk Eli Zaretskii
2011-02-05 9:52 ` Katsumi Yamaoka
2011-02-05 11:47 ` Eli Zaretskii
2011-02-05 12:16 ` Katsumi Yamaoka
2011-02-07 18:29 ` Ted Zlatanov
2011-02-08 3:49 ` Eli Zaretskii
2011-02-08 8:00 ` Peter Münster
2011-02-08 8:28 ` Eli Zaretskii
2011-02-08 8:50 ` Andreas Schwab
2011-02-08 9:06 ` Peter Münster
2011-02-08 9:28 ` Eli Zaretskii
2011-02-08 14:33 ` -DWEBHACKDEVEL for Gnus (was: Revision 103117 on the Emacs trunk.) Ted Zlatanov
2011-02-08 15:23 ` -DWEBHACKDEVEL for Gnus Peter Münster
2011-02-05 13:08 ` Revision 103117 on the Emacs trunk Andreas Schwab
2011-02-05 14:21 ` Gnus overrides.texi and WEBHACKDEVEL (was: Revision 103117 on the Emacs trunk.) Ted Zlatanov
2011-02-05 15:12 ` Gnus overrides.texi and WEBHACKDEVEL Eli Zaretskii
2011-02-05 15:18 ` Ted Zlatanov
2011-02-05 15:39 ` Eli Zaretskii
2011-02-05 16:01 ` Ted Zlatanov [this message]
2011-02-07 19:06 ` Eli Zaretskii
2011-02-07 19:19 ` Ted Zlatanov
2011-02-07 19:47 ` Eli Zaretskii
2011-02-06 6:49 ` Stephen J. Turnbull
2011-02-06 10:25 ` Eli Zaretskii
2011-02-06 14:40 ` Stephen J. Turnbull
2011-02-06 17:22 ` Eli Zaretskii
2011-02-06 17:52 ` Stephen J. Turnbull
2011-02-06 18:50 ` Eli Zaretskii
2011-02-06 19:20 ` Stephen J. Turnbull
2011-02-06 21:21 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y65ua2s5.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).