From: Jeffrey A Law <law@cygnus.com>
To: Dave Love <d.love@dl.ac.uk>
Cc: egcs@cygnus.com
Subject: Re: Direct CVS Access to egcs sources
Date: Sun, 08 Feb 1998 10:14:00 -0000 [thread overview]
Message-ID: <11780.886961802@hurl.cygnus.com> (raw)
In-Reply-To: <rzq90rmhw5n.fsf@djlvig.dl.ac.uk>
In message < rzq90rmhw5n.fsf@djlvig.dl.ac.uk >you write:
> Why isn't the usual `ident' mechanism appropriate, given you can't
> guarantee the integrity of a given set of sources, even WRT a given
> date? Do the potentially-annoying problems with patches swing it or
> something else?
RCS keyword expansion is a pain to deal with when merging in changes from
multiple source trees.
One of the things on my long term todo list is to find the few remaining
keywords in egcs and kill them.
jeff
next prev parent reply other threads:[~1998-02-08 10:14 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-01-13 4:52 Jeffrey A Law
1998-01-14 8:18 ` Oleg Krivosheev
1998-01-14 8:42 ` Jeffrey A Law
1998-01-15 16:06 ` Joe Buck
1998-01-15 16:30 ` Jeffrey A Law
1998-01-16 1:51 ` Joe Buck
1998-02-08 0:29 ` Jeffrey A Law
1998-02-08 7:13 ` Gerald Pfeifer
1998-02-08 8:57 ` Dave Love
1998-02-08 10:14 ` Jeffrey A Law [this message]
1998-02-08 13:23 ` H.J. Lu
1998-02-08 15:38 ` Jeffrey A Law
1998-02-08 15:20 ` H.J. Lu
1998-02-08 15:38 ` Jeffrey A Law
1998-02-08 18:35 ` Todd Vierling
1998-02-08 15:38 ` Bryan W. Headley
1998-01-17 22:30 ` Raja R Harinath
1998-01-15 16:30 ` Robert Lipe
1998-01-16 2:26 ` Jeffrey A Law
1998-01-15 16:30 ` Franz Sirl
1998-01-17 1:40 ` Robert Lipe
1998-01-17 22:30 ` Joseph H. Buehler
1998-01-19 2:25 ` Robert Lipe
1998-01-19 2:30 ` Jeffrey A Law
1998-01-19 2:30 ` Fred Fish
1998-01-20 4:00 Mike Stump
[not found] <199801142227.OAA03715@cygnus.com>
1998-01-23 0:20 ` Jeffrey A Law
1998-01-23 11:15 ` Franz Sirl
[not found] <199801231742.JAA01350@cygnus.com>
1998-01-23 9:47 ` Jeffrey A Law
[not found] <19980209020929.50632@cerebro.laendle>
1998-02-08 22:42 ` Jeffrey A Law
1998-02-09 19:49 ` Joern Rennecke
1998-02-09 21:34 ` Jeffrey A Law
1998-02-11 10:25 ` Marc Lehmann
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=11780.886961802@hurl.cygnus.com \
--to=law@cygnus.com \
--cc=d.love@dl.ac.uk \
--cc=egcs@cygnus.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).