From: Nick Roberts <nickrob@snap.net.nz>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org, rms@gnu.org, miles@gnu.org
Subject: Re: ugliness in simple.el CVS log
Date: Mon, 23 Apr 2007 21:40:17 +1200 [thread overview]
Message-ID: <17964.32513.963688.349449@farnswood.snap.net.nz> (raw)
In-Reply-To: <ufy6rxx5z.fsf@gnu.org>
> > > ??? How can CVS comments break or postpone the release? They don't
> > > affect any file that goes into the tarball.
> >
> > Not CVS comments but "cvs admin". The CVS manual says:
> >
> > admin options
> > -------------
> >
> > ...Some even make it impossible to use CVS until
> > you undo the effect!
> >
> > Anything that requires admin (cvsadmin) privileges is usually pretty dangerous
> > but, in any case, the onus is on the person making the change to convince
> > others that it is safe ("I done this many times and never had a problem."),
> > rather than on me to prove it isn't.
>
> Please let's trust Miles that he knows his way with "cvs admin -m".
> He's one of the few project admins for a very good reason.
It's not just one file as Thi suggests, and AFAIK logs and code are stored in
the same files. The reason for having few project admins can only be that
it's easy to mess things up. Since, as you say, the correct change doesn't
affect any file that goes into the tarball, why take any risk, however small?
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2007-04-23 9:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-23 3:48 ugliness in simple.el CVS log Richard Stallman
2007-04-23 4:09 ` Miles Bader
2007-04-23 4:35 ` Nick Roberts
2007-04-23 8:34 ` Eli Zaretskii
2007-04-23 8:59 ` Nick Roberts
2007-04-23 9:13 ` Thien-Thi Nguyen
2007-04-23 9:22 ` Eli Zaretskii
2007-04-23 9:40 ` Nick Roberts [this message]
2007-04-23 11:03 ` Thien-Thi Nguyen
2007-04-23 12:06 ` Eli Zaretskii
2007-04-23 23:07 ` Richard Stallman
2007-04-24 21:26 ` Miles Bader
-- strict thread matches above, loose matches on Subject: below --
2007-04-15 13:58 Richard Stallman
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=17964.32513.963688.349449@farnswood.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=miles@gnu.org \
--cc=rms@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).