From: Kevin Buettner <kevinb@cygnus.com>
To: Andrew Cagney <ac131313@cygnus.com>, gdb@sources.redhat.com
Subject: Re: Are RCS ID's bad?
Date: Thu, 09 Aug 2001 12:28:00 -0000 [thread overview]
Message-ID: <1010809192757.ZM11800@ocotillo.lan> (raw)
In-Reply-To: <3B72DD76.2010609@cygnus.com>
On Aug 9, 2:59pm, Andrew Cagney wrote:
> 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?
FWIW, I'm all in favor of getting rid of them. I once did a merge (in
a different tree) between the trunk and a branch which had a lot of
conflicts. Over ninety percent of them were due to RCS identifiers.
Kevin
next prev parent reply other threads:[~2001-08-09 12:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-09 11:59 Andrew Cagney
2001-08-09 12:28 ` Kevin Buettner [this message]
2001-08-09 13:20 Mcspadden, William C
2001-08-09 22:40 ` Andrew Cagney
2001-08-10 2:53 ` Richard Earnshaw
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=1010809192757.ZM11800@ocotillo.lan \
--to=kevinb@cygnus.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