Gnus development mailing list
 help / color / mirror / Atom feed
From: Russ Allbery <rra@stanford.edu>
Subject: Re: committing in the CVS archive
Date: 04 Oct 1999 14:02:22 -0700	[thread overview]
Message-ID: <ylvh8malgh.fsf@windlord.stanford.edu> (raw)
In-Reply-To: Wes Hardaker's message of "04 Oct 1999 13:56:59 -0700"

Wes Hardaker <wjhardaker@ucdavis.edu> writes:

> The latest and greatest cvs actually has built in mailing code, and
> doesn't look that bad...  Umm....  Example:

> From: Wes Hardaker <wjhardaker@ucdavis.edu>
> Subject: CVS update: ucd-snmp
> To: ucd-snmp-cvs@ucd-snmp.ucdavis.edu
> Date: Mon, 4 Oct 1999 13:51:54 -0700 (PDT)

> Date:	Monday October 4, 1999 @ 13:51
> Author:	hardaker

> Update of /opt/ucd-snmp/ucd-snmp/agent/mibgroup/mibII
> In directory ucd-snmp:/tmp/cvs-serv14408

> Modified Files:
> 	system_mib.c 
> Log Message:
> - (system_mib.c): make sysServices configurable.

That looks like it went through one of the preprocessor scripts that comes
with CVS, actually.  Mine is similar but it does more rewriting; it adds
some blank lines, lines up the headers, moves the tag up into the subject
header, distinguishes between new directories and other commits, puts a
file list in the Subject line abbreviated to a file count if it's too
long, and a few other random things along those lines.

-- 
Russ Allbery (rra@stanford.edu)         <URL:http://www.eyrie.org/~eagle/>


  reply	other threads:[~1999-10-04 21:02 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
1999-10-04 20:56     ` Wes Hardaker
1999-10-04 21:02       ` Russ Allbery [this message]
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=ylvh8malgh.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).