From: Jeffrey A Law <law@hurl.cygnus.com>
To: Jan Reimers <janr@molienergy.bc.ca>
Cc: "'egcs@cygnus.com'" <egcs@cygnus.com>
Subject: Re: Can we remove bison output from cvs?
Date: Sun, 31 Jan 1999 23:58:00 -0000 [thread overview]
Message-ID: <15964.916720752@hurl.cygnus.com> (raw)
In-Reply-To: <71B30885B657D111809D080009EEBBF34FE6D2@MAILSERV.molienergy.bc.ca>
In message < 71B30885B657D111809D080009EEBBF34FE6D2@MAILSERV.molienergy.bc.ca >
you write:
> It seems CVS 1.10 does not support what we need to do in the modules
> file, namely:
>
> #start CVSROOT/modules
> auto_generated_files -a {big list of auto generated files}
>
> egcs_noauto -a !auto_generated_files egcs
> #start CVSROOT/modules
>
> the cvs modules parsing code does support the ignore directive, but ONLY
> for directories, NOT for aliases (as I show above) or for individual
> file names.
Bummer.
> I didn't bother looking and non-release versions of cvs
> like 1.10.{1->4} since I suspect few if any egcs users will be running
> these versions.
This kind of functionality would probably be server side only, which wouldn't
require an update of the end-user client. We need to upgrade anyway, so if
some new version has such a feature, it's just one more reason to bite the
bullet and upgrade cvs on the server.
> Anybody know what the cvs developers are up to in the area?
> Would they accept a patch from an unknown?
Dunno. You might head over to cyclic's home page and see if they mention
anything interesting.
> As for checking out things like egcs-core, egcs-g++, egcs-java
> etc. I can try and set that up if it is useful.
Yes, I think this would still be very useful
jeff
next prev parent reply other threads:[~1999-01-31 23:58 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-31 23:58 Jan Reimers
1999-01-31 23:58 ` Jeffrey A Law [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-01-31 23:58 Jan Reimers
1999-01-31 23:58 ` Jeffrey A Law
1999-01-31 23:58 ` Bruce Korb
1999-01-31 23:58 Mike Stump
1999-01-31 23:58 Kaveh R. Ghazi
1999-01-31 23:58 ` Per Bothner
1999-01-31 23:58 N8TM
1999-01-31 23:58 Kaveh R. Ghazi
1999-01-31 23:58 ` Jeffrey A Law
1999-01-31 23:58 Per Bothner
1999-01-31 23:58 ` Bill Currie
1999-01-31 23:58 ` Jeffrey A Law
1999-01-31 23:58 ` Joe Buck
1999-01-31 23:58 ` Jeffrey A Law
1999-01-31 23:58 ` Per Bothner
1999-01-31 23:58 ` David Starner
1999-01-31 23:58 ` Joe Buck
1999-01-31 23:58 ` Jeffrey A Law
1999-01-31 23:58 ` Marc Espie
1999-01-31 23:58 Kaveh R. Ghazi
1999-01-31 23:58 ` Joern Rennecke
1999-01-31 23:58 ` Per Bothner
1999-01-31 23:58 ` Gerald Pfeifer
1999-01-31 23:58 ` Marc Lehmann
1999-01-31 23:58 ` Bruce Korb
1999-01-31 23:58 ` Joern Rennecke
1999-01-31 23:58 ` Bruce Korb
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=15964.916720752@hurl.cygnus.com \
--to=law@hurl.cygnus.com \
--cc=egcs@cygnus.com \
--cc=janr@molienergy.bc.ca \
/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).