From: Wes Hardaker <wjhardaker@ucdavis.edu>
Subject: Re: CVS write access policy & nntp gateway & bug reports & stuff
Date: 04 Oct 1999 08:59:31 -0700 [thread overview]
Message-ID: <sd670n6rrw.fsf@homestyle.dcn.davis.ca.us> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "27 Sep 1999 18:40:44 +0200"
>>>>> On 27 Sep 1999 18:40:44 +0200, Lars Magne Ingebrigtsen <larsi@gnus.org> said:
Lars> Oh, but pleeeze -- please update the ChangeLog when you do any
Lars> changes.
You might consider generating the ChangeLog file from the cvs log
messages... I do this and that way I don't have to worry about people
updating the ChangeLog file. Of course, teaching them to write
properly formatted commit messages is sometimes equally a pain...
I have a perl script if ya like...
--
"Ninjas aren't dangerous. They're more afraid of you than you are of them."
next prev parent reply other threads:[~1999-10-04 15:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-27 16:05 just tried making 0.97 Daniel Monjar
1999-09-27 16:14 ` Ted Rathkopf
1999-09-27 16:29 ` Lars Magne Ingebrigtsen
1999-09-27 16:40 ` CVS write access policy & nntp gateway & bug reports & stuff Lars Magne Ingebrigtsen
1999-10-04 15:59 ` Wes Hardaker [this message]
1999-10-08 15:43 ` Robert Bihlmeyer
1999-09-27 17:00 ` just tried making 0.97 Stainless Steel Rat
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=sd670n6rrw.fsf@homestyle.dcn.davis.ca.us \
--to=wjhardaker@ucdavis.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).