From: Miles Bader <miles@lsi.nec.co.jp>
Cc: emacs-devel@gnu.org
Subject: Re: RCS keyword removal
Date: 12 Apr 2004 10:48:37 +0900 [thread overview]
Message-ID: <buo8yh2klu2.fsf@mcspd15.ucom.lsi.nec.co.jp> (raw)
In-Reply-To: <1081703812.770.131.camel@localhost>
Andre Spiegel <spiegel@gnu.org> writes:
> A general approach might be to switch off keyword expansion for
> anything that is checked in to Arch.
I'd like to do this, but have been nervous to because of my uncertainity
about CVS's behavior. If people think it's safe to use `-kb' globally
I'll do that (from from my reading of the docs a global `-ko' is
dangerous though, as it overrides a file-specific -kb setting, and so
could conceivably cause problems with binary files).
If I'm interpreting the docs correctly, BTW, switching to `-kb' will
leave expanded keywords in currently checked-out files unchanged (that
is, if CVS stores keywords unexpanded in the repository, adding `-kb'
_won't_ suddently cause keywords in checked out files to revert to their
unexpanded forms), which might be slightly confusing for anyone relying
on RCS keywords in bug reports.
> Alternatively, a feature to tell Arch to ignore certain kinds of
> differences could be implemented.
But I'm not going to do that.
Thanks,
-Miles
--
97% of everything is grunge
next prev parent reply other threads:[~2004-04-12 1:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-10 6:00 RCS keyword removal Miles Bader
2004-04-11 15:18 ` Andre Spiegel
2004-04-11 15:51 ` Miles Bader
2004-04-11 16:06 ` Andreas Schwab
2004-04-11 17:16 ` Andre Spiegel
2004-04-12 1:48 ` Miles Bader [this message]
2004-04-12 9:14 ` Andre Spiegel
2004-04-12 9:27 ` Miles Bader
2004-04-13 9:10 ` Miles Bader
2004-04-13 9:29 ` Andre Spiegel
2004-04-13 10:00 ` Miles Bader
2004-04-12 21:28 ` Kim F. Storm
2004-04-13 1:18 ` Miles Bader
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=buo8yh2klu2.fsf@mcspd15.ucom.lsi.nec.co.jp \
--to=miles@lsi.nec.co.jp \
--cc=emacs-devel@gnu.org \
--cc=miles@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.