From: Richard Earnshaw <rearnsha@arm.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: "Mcspadden, William C" <william.c.mcspadden@intel.com>,
gdb@sources.redhat.com, Richard.Earnshaw@arm.com
Subject: Re: Are RCS ID's bad?
Date: Fri, 10 Aug 2001 02:53:00 -0000 [thread overview]
Message-ID: <200108100952.KAA00622@cam-mail2.cambridge.arm.com> (raw)
In-Reply-To: <3B737387.4090803@cygnus.com>
The NetBSD folks use $NetBSD: .. $ instead of $Id: $. The great advantage
of this is that if the file is imported into another repository, or if a
foreign file is imported into NetBSD's repository, then the master Id
numbers are preserved.
If you are going to keep using such tags, I'd strongly encourage you to
consider a similar approach ... $GNU:...$?
R.
next prev parent reply other threads:[~2001-08-10 2:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-09 13:20 Mcspadden, William C
2001-08-09 22:40 ` Andrew Cagney
2001-08-10 2:53 ` Richard Earnshaw [this message]
-- 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=200108100952.KAA00622@cam-mail2.cambridge.arm.com \
--to=rearnsha@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=ac131313@cygnus.com \
--cc=gdb@sources.redhat.com \
--cc=william.c.mcspadden@intel.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