From: Zefram <zefram@fysh.org>
To: Peter Stephenson <pws@pwstephenson.fsnet.co.uk>
Cc: Zsh hackers list <zsh-workers@sunsite.auc.dk>
Subject: Re: sourceforge issues
Date: Tue, 4 Apr 2000 00:00:54 +0100 (BST) [thread overview]
Message-ID: <E12cFq2-00046R-00@crucigera.fysh.org> (raw)
In-Reply-To: <E12cDij-0004C5-00.2000-04-03-21-45-13@mail3.svr.pol.co.uk> from Peter Stephenson at "Apr 3, 2000 09:45:11 pm"
Peter Stephenson wrote:
>- Sven (and everyone else), I'm afraid you're now responsible for adding
> your own ChangeLog entries, ideally in the same commit. Bummer. (Tee,
> hee, hee.)
Feature. The lack of this kind of convention is one of the things that
bugged me about the old single-maintainer repository system.
>- Geoff, I agree the number of tags makes things difficult. I won't be
> adding per-patch tags myself, though I can see the point of it since CVS
> doesn't make it easy for you to regenerate a patch otherwise. It
> would probably be good to remove the old ones, though it's quite useful
> to be able to go straight to what a patch did.
In my personal repository, I always used to include the patch number
(from the mailing list) in the log message. This doesn't make it *easy*
to extract the patch from the archive, but it makes it possible (it
certainly points you towards a good set of date tags to compare), and in
cases where the patch exists separately (e.g., it's on the mailing list)
it provides a handy reference. If we're going to have patches in CVS
that don't appear on the mailing list, it's still possible to come up with
unique IDs: we just need to each keep track of our own sequence numbers.
> As far as I can see the cvsweb.cgi interface needs you to tell it a
> version number which would put paid to this. The may be some feature
> I haven't seen.
The pseudo-label "HEAD" is supposed to evaluate to the latest
version on the trunk. Does this web interface accept version labels?
-zefram
next prev parent reply other threads:[~2000-04-03 23:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-03 20:45 Peter Stephenson
2000-04-03 21:50 ` Adam Spiers
2000-04-04 0:13 ` Bart Schaefer
2000-04-03 21:52 ` Clint Adams
2000-04-04 19:38 ` Peter Stephenson
2000-04-03 22:14 ` Bruce Stephens
2000-04-03 23:00 ` Zefram [this message]
2000-04-04 0:09 ` Bart Schaefer
2000-04-04 0:14 ` Chmouel Boudjnah
2000-04-04 19:31 ` Peter Stephenson
2000-04-04 1:27 ` Geoff Wing
2000-04-04 3:23 ` Clint Adams
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=E12cFq2-00046R-00@crucigera.fysh.org \
--to=zefram@fysh.org \
--cc=pws@pwstephenson.fsnet.co.uk \
--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).