unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Miles Bader <miles@gnu.org>
Cc: emacs-devel@gnu.org, Miles Bader <miles@gnu.org>
Subject: Re: RCS keyword removal
Date: Tue, 13 Apr 2004 06:00:38 -0400	[thread overview]
Message-ID: <20040413100038.GA10307@fencepost> (raw)
In-Reply-To: <1081848593.770.160.camel@localhost>

On Tue, Apr 13, 2004 at 11:29:53AM +0200, Andre Spiegel wrote:
> I think you need to use "cvs co -kk ...".  That explicitly resets the
> keywords to their unexpanded form.  It seems that -kb reverts to
> whatever form the keyword happens to have in the RCS master file, which
> is bogus because it is rewritten upon checkout anyway.  So, -kk ought to
> be the right option.

Since co/update -k options override all file-specific settings (and thus
might screw up binary files if used globally) I guess what I should do is
checkout only those few files in emacs that still use RCS keywords using -kk
and rely on the fact that it's a sticky option.  [It's a shame because it
would seem to be a much more robust solution to somehow have the CVS/arch
gateway script do it.]

Thanks,

-Miles
-- 
A zen-buddhist walked into a pizza shop and
said, "Make me one with everything."

  reply	other threads:[~2004-04-13 10:00 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
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 [this message]
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

  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=20040413100038.GA10307@fencepost \
    --to=miles@gnu.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.
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).