From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: Patching (was: Re: PATCH: AIX dep.&doc fix; development guidelines)
Date: Mon, 10 Apr 2000 10:03:02 +0200 (MET DST) [thread overview]
Message-ID: <200004100803.KAA13671@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: Sven Wischnowsky's message of Mon, 10 Apr 2000 09:26:31 +0200 (MET DST)
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@informatik.hu-berlin.de
next reply other threads:[~2000-04-10 8:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-10 8:03 Sven Wischnowsky [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-04-10 7:26 Sven Wischnowsky
2000-04-17 11:14 ` Geoff Wing
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=200004100803.KAA13671@beta.informatik.hu-berlin.de \
--to=wischnow@informatik.hu-berlin.de \
--cc=zsh-workers@sunsite.auc.dk \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).