From: Luca Benini <lbenini@csr.unibo.it>
To: Patrick McFarland <unknown@panax.com>
Cc: gcc@gcc.gnu.org
Subject: Re: About #sccs
Date: Mon, 06 Dec 2004 10:48:00 -0000 [thread overview]
Message-ID: <41B43904.4040606@csr.unibo.it> (raw)
In-Reply-To: <200412060526.31263.unknown@panax.com>
Patrick McFarland wrote:
> On Monday 06 December 2004 03:39, Luca Benini wrote:
>
>>[Sun FORTRAN 77 4.0 User Guide)
>>Some developers put one or more SCCS ID keywords into each file, but
>>that is optional. These keywords are later identified with a version
>>number each time the files are checked in with an SCCS get or delget
>>command. There are three likely places to put these strings:[...]
>
>
> So its something like CVS's $Id$?
>
Yes.
--
But how can I implement unimaginable chaos in my compiler?
-Geerhardt Goos-
next prev parent reply other threads:[~2004-12-06 10:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-06 8:39 Luca Benini
2004-12-06 10:28 ` Patrick McFarland
2004-12-06 10:48 ` Luca Benini [this message]
2004-12-06 12:24 ` Nathan Sidwell
2004-12-06 16:30 ` Luca Benini
2004-12-06 17:39 ` Manfred Hollstein
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=41B43904.4040606@csr.unibo.it \
--to=lbenini@csr.unibo.it \
--cc=gcc@gcc.gnu.org \
--cc=unknown@panax.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).