zsh-workers
 help / color / mirror / code / Atom feed
From: Zefram <zefram@fysh.org>
To: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
Cc: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: AIX dep.&doc fix; development guidelines
Date: Thu, 6 Apr 2000 17:23:16 +0100 (BST)	[thread overview]
Message-ID: <E12dF3s-00019H-00@crucigera.fysh.org> (raw)
In-Reply-To: <200004060723.JAA06359@beta.informatik.hu-berlin.de> from Sven Wischnowsky at "Apr 6, 2000 09:23:49 am"

Sven Wischnowsky wrote:
>> But with e.g. my patch to Makefile.in, I mailed off the "cvs diff" output
>> and then waited for the patch to come back to me before committing, so I
>> could reference the article number in the commitlog.  It appears that Sven
>> has been doing this too.
>
>Yesss, most annoying... it means that I can't continue hacking on the
>next thing before the mail comes back. So zsh interrupts my real work
>more often and in smaller time slices.

This is obviously getting in the way of things.  I think we'll have to
abandon the ideal of having mailing list message numbers in commit log
entries and in ChangeLog entries (at least as initially committed).
Let's just each use our own sequence numbers, and rely on grep to tie
the CVS changes to the mailing list message.

-zefram


  reply	other threads:[~2000-04-06 16:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-06  7:23 Sven Wischnowsky
2000-04-06 16:23 ` Zefram [this message]
2000-04-06 17:02   ` Bart Schaefer
2000-04-06 17:27     ` Zefram
2000-04-06 17:39       ` Bart Schaefer
2000-04-06 17:51         ` Zefram
2000-04-06 23:12           ` Bart Schaefer
2000-04-07 20:04             ` Peter Stephenson
2000-04-08 22:09               ` Bart Schaefer
  -- strict thread matches above, loose matches on Subject: below --
2000-04-07  8:38 Sven Wischnowsky
2000-04-05 16:52 Oliver Kiddle
2000-04-05 18:06 ` Bart Schaefer
2000-04-05 19:21   ` Peter Stephenson
2000-04-05 19:43     ` Peter Stephenson
2000-04-05 20:41     ` Bart Schaefer

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=E12dF3s-00019H-00@crucigera.fysh.org \
    --to=zefram@fysh.org \
    --cc=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).