Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Patching (was: Re: PATCH: AIX dep.&doc fix; development guidelines)
- X-seq: zsh-workers 10610
- From: Sven Wischnowsky <wischnow@xxxxxxxxxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxxxxxx
- Subject: Re: Patching (was: Re: PATCH: AIX dep.&doc fix; development guidelines)
- Date: Mon, 10 Apr 2000 10:03:02 +0200 (MET DST)
- In-reply-to: Sven Wischnowsky's message of Mon, 10 Apr 2000 09:26:31 +0200 (MET DST)
- Mailing-list: contact zsh-workers-help@xxxxxxxxxxxxxx; run by ezmlm
I wrote:
> Peter Stephenson wrote:
>
> > Bart Schaefer wrote:
> > > At the time an actual release is done, will the maintainer (hi, Peter)
> > > please do a sweep of the ChangeLog and convert all the "zefram1XX" etc.
> > > into the actual article numbers?
> >
> > Ouch. Script?
>
> I've had an idea at the weekend, but don't know if this is possible
> with a (remote) CVS server, so I'll have to ask some questions...
>
> Using `loginfo', it should be possible to make the CVS server give out
> numbers for the patches, err... for the commits. If the program
> executed from loginfo prints something, will that be displayed on the
> terminal where one does the commit? With a local repository this seems
> to work. If it works with remote CVS, too, we probably could make the
> loginfo-program get the number and print, at the end of the
> commit-output (or somewhere in-between), something like `Commit number xxx'.
I forgot: reporting the number on the commit would allow us to include
it in the mail without having to wait for the mail to come back.
Probably in a subject like `PATCH:xxx:...'. And maybe the mail archive
could then allow to access them with `http://.../xxx'?
Bye
Sven
--
Sven Wischnowsky wischnow@xxxxxxxxxxxxxxxxxxxxxxx
Messages sorted by:
Reverse Date,
Date,
Thread,
Author