From: Christoph Conrad <cc@cli.de>
Subject: Re: Customizing article expiry
Date: Mon, 07 Jan 2002 17:58:42 +0100 [thread overview]
Message-ID: <uell2hzct.fsf@cli.de> (raw)
In-Reply-To: <m37kquw241.fsf@multivac.cwru.edu> (prj@po.cwru.edu's message of "Mon, 07 Jan 2002 11:35:04 -0500")
Hello Paul,
you wrote:
>> Where are you guys getting these recent ChangeLogs? When I run
>> `cvs update' today 01/07 The ChangeLog is ancient. Most recent
>> entry is 01/02/02.
Paul> $ find . -name ChangeLog -print -exec head -1 '{}' \;
There's a very fine tool available at
http://www.red-bean.com/cvs2cl/
,----
| This Perl script does what you think it does: it produces a GNU-style
| ChangeLog for CVS-controlled sources, by running "cvs log" and parsing
| the output. Duplicate log messages get unified in the Right Way. If
| you don't know what any of that means, then you're doing fine, just
| keep on truckin' (i.e., hit the Back button on your browser).
`----
It works recursively on a CVS tree and has some options for
controlling the output.
I call it (on Windows NT) from a batchfile with
,----
| @perl.exe -S cvs2cl.pl -S --no-wrap %1 %2 %3 %4 %5 %6 %7 %8 %9
`----
Best regards,
Christoph Conrad
--
TTi Entwicklungszentrum GmbH, Elisabethstr. 16, D-52062 Aachen
Fon: +49 241 47051-0 Fax: +49 241 47051-89 Web: http://www.ttisystems.com
-
There are 3 kinds of people, those who can count and those who can't.
next prev parent reply other threads:[~2002-01-07 16:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <u1u153jr.fsf@online.no>
[not found] ` <m1k7uwda8b.fsf@reader.newsguy.com>
[not found] ` <m3u1u08yxy.fsf@quimbies.gnus.org>
[not found] ` <x7n0zrpgzu.fsf@reader.newsguy.com>
[not found] ` <1yh3pf0x.fsf@online.no>
2002-01-07 16:28 ` Harry Putnam
2002-01-07 16:35 ` Paul Jarc
2002-01-07 16:58 ` Christoph Conrad [this message]
2002-01-07 18:35 ` Harry Putnam
2002-01-07 18:48 ` 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=uell2hzct.fsf@cli.de \
--to=cc@cli.de \
--cc=christoph.conrad@gmx.de \
/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).