Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Mcspadden, William C" <william.c.mcspadden@intel.com>
To: "'Andrew Cagney'" <ac131313@cygnus.com>, gdb@sources.redhat.com
Subject: RE: Are RCS ID's bad?
Date: Thu, 09 Aug 2001 13:20:00 -0000	[thread overview]
Message-ID: <9287DC1579B0D411AA2F009027F44C3F064FAEE5@FMSMSX41> (raw)

I find the RCS keywords useful (except for $Log$) and would not
recommend deleting them. 

For purposes of merges and diffs, keyword expansion can be suppressed
by cvs when you do a checkout. See chapter 12 of the CVS manual for
a discussion of this. 

This eliminated the many problems I had when doing merges caused by
the very thing you describe. However, it didn't eliminate the problems
with the $Log$ expansion. Just don't use $Log$.

Bill Mc.

> -----Original Message-----
> From: Andrew Cagney [ mailto:ac131313@cygnus.com ]
> Sent: Thursday, August 09, 2001 11:59 AM
> To: gdb@sources.redhat.com
> Subject: Are RCS ID's bad?
> 
> 
> Hello,
> 
> I'm considering deleting any line containing something like:
> 
> 	$Id: .... $
> 
> ($Date: ..$; ....) from the GDB source tree.  They make a 
> right mess of 
> merges, diffs, compares and the like.
> 
> Can anyone come up with a reason to retain these?
> 
> GDB has gdb/version.in as a revision identifier.  Going by recent 
> e-mail's this is proving very effective - people are identifying GDB 
> snapshots and checkouts by date (although sometimes the 
> quoted dates are 
> backwards :-)
> 
> 	Andrew
> 
> 


             reply	other threads:[~2001-08-09 13:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-09 13:20 Mcspadden, William C [this message]
2001-08-09 22:40 ` Andrew Cagney
2001-08-10  2:53   ` Richard Earnshaw
  -- strict thread matches above, loose matches on Subject: below --
2001-08-09 11:59 Andrew Cagney
2001-08-09 12:28 ` Kevin Buettner

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=9287DC1579B0D411AA2F009027F44C3F064FAEE5@FMSMSX41 \
    --to=william.c.mcspadden@intel.com \
    --cc=ac131313@cygnus.com \
    --cc=gdb@sources.redhat.com \
    /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