Re: Patching (was: Re: PATCH: AIX dep.&doc fix; development guidelines)

Re: Patching (was: Re: PATCH: AIX dep.&doc fix; development guidelines)

[Sven Wischnowsky]

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

Re: Patching (was: Re: PATCH: AIX dep.&doc fix; development guidelines)

[Geoff Wing]

Sven Wischnowsky <wischnow@informatik.hu-berlin.de> typed:
: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 :pserver: it will.  I presume it also will with ssh.

: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'.

Yes, though if you want a sequence then you'll need to have it do its
own locking on whatever file (presumably kept in CVSROOT/) contains
the number.

:Next question: could loginfo (or some of the other automatically
:executed things) append that number to the log-message given to the
:commit? So that we also have the number in the messages stored in the
:repository.

Not within the normal CVS pathway.  The only CVSROOT/* file which can
modify the checkin is cvswrappers (unless you have one of the others
spawn some program which does it own hacking - very dangerous) and
cvswrappers modifies the _file_ not the log message.  And hope nobody
makes drastic changes with ``cvs admin -m....'' independent of the
ChangeLog; probably not a problem (though IIRC in one or more versions
of cvs you could damage your file/s using that - or maybe that was
``cvs admin -o'' and we hope that nobody is going to use that).

:And finally, if all the above works, the CVS server has the
:log-message from the user, the patch number and it knows the changed
:files, so: could it change ChangeLog automatically?

I can't think of any elegant way to do so (on the remote CVS server)
since you have no properly safe work space (except maybe /{,usr/,var/}tmp).
You could have ChangeLog centrally managed off-site, e.g. have loginfo
mail in some special format to, say, orbital/shell1 and reconstructed
there into something which can be automagically prepended to ChangeLog.
If someone gets really, really sick of updating ChangeLog they can look
into that :-)

Regards,
-- 
Geoff Wing : <gcw@pobox.com>     Work URL: http://www.primenet.com.au/
Rxvt Stuff : <gcw@rxvt.org>      Ego URL : http://pobox.com/~gcw/
Zsh Stuff  : <gcw@zsh.org>       Phone   : (Australia) 0413 431 874

Patching (was: Re: PATCH: AIX dep.&doc fix; development guidelines)

[Sven Wischnowsky]

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'.

Next question: could loginfo (or some of the other automatically
executed things) append that number to the log-message given to the
commit? So that we also have the number in the messages stored in the
repository.

And finally, if all the above works, the CVS server has the
log-message from the user, the patch number and it knows the changed
files, so: could it change ChangeLog automatically?


Is any or all of this possible?

Bye
 Sven


--
Sven Wischnowsky                         wischnow@informatik.hu-berlin.de