zsh-workers
 help / color / mirror / code / Atom feed
From: mason@primenet.com.au (Geoff Wing)
To: zsh-workers@sunsite.auc.dk
Subject: More SourceForge issues (Was: Completion issues)
Date: 4 Apr 2000 10:30:52 GMT	[thread overview]
Message-ID: <slrn8ejh2s.aga.mason@coral.primenet.com.au> (raw)
In-Reply-To: <200004040949.LAA05373@beta.informatik.hu-berlin.de>

Sven Wischnowsky <wischnow@informatik.hu-berlin.de> typed:
:I've update the ChangeLog for the stuff from yesterday... but rcs2log
:is completely unusable for me because it takes ages (so long that I
:haven't let it run until the end).

rcs2log is really only useful for generating your own ChangeLog entry.
Previous commits by someone else which aren't in the ChangeLog would
need manual adjustment of names & email addresses.  Even if run on
sourceforge (to speed it up) it would still need email addresses updated.
However, I might have missed the decision on how ChangeLog is to be
updated but I would have presumed that people would use useful commit
messages and then the ChangeLog could be generated just before a release
from those messages (and name/email addresses can be replaced then) - the
only real difference to our current ChangeLog format being that files
affected are also listed (and it might not be quite as pretty)

:Is there a tool to get a ChangeLog
:entry template from a diff? Or do I have to write that myself?

One other option is to overload the (currently) theoretical aggregating
commit message tool to also dump info out to some other area (although this
is more complicated since it's hosted on another machine to that we can
run tools on).  Of course, if each developer is responsible for updating
ChangeLog hirself then just save the commit message file to something else
when you're committing and then you've got it handy.
(Or the longer way would be do rcs2log on just those files you updated and
use the appropriate part of ChangeLog generated).

Do people on zsh-workers want to see all these SourceForge messages (to
keep abreast with what's happening or whatever) or is it more suitable
off this list to amongst those developing on SourceForge?

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


      reply	other threads:[~2000-04-04 10:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-04  9:49 Completion issues Sven Wischnowsky
2000-04-04 10:30 ` Geoff Wing [this message]

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=slrn8ejh2s.aga.mason@coral.primenet.com.au \
    --to=mason@primenet.com.au \
    --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).