From: Russ Allbery <rra@stanford.edu>
Subject: Re: committing in the CVS archive
Date: 04 Oct 1999 09:37:23 -0700 [thread overview]
Message-ID: <ylg0zrdqv0.fsf@windlord.stanford.edu> (raw)
In-Reply-To: Wes Hardaker's message of "04 Oct 1999 09:05:32 -0700"
Wes Hardaker <wjhardaker@ucdavis.edu> writes:
> I suggest making it happen... Definitely a plus to doing multiple
> developer CVS repositories.
I can scrounge up the Perl script that I use for CVS commit logging at
work and for INN development, if people are interested. It runs from
loginfo and cleans up the raw CVS output a little to make it more
readable.
--
Russ Allbery (rra@stanford.edu) <URL:http://www.eyrie.org/~eagle/>
next prev parent reply other threads:[~1999-10-04 16:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-30 9:36 Didier Verna
1999-09-30 9:42 ` Norbert Koch
1999-10-04 16:05 ` Wes Hardaker
1999-10-04 16:37 ` Russ Allbery [this message]
1999-10-04 20:56 ` Wes Hardaker
1999-10-04 21:02 ` Russ Allbery
1999-11-06 2:07 ` Lars Magne Ingebrigtsen
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=ylg0zrdqv0.fsf@windlord.stanford.edu \
--to=rra@stanford.edu \
/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 NNTP newsgroup(s).