zsh-workers
 help / color / mirror / code / Atom feed
From: Bruce Stephens <B.Stephens@isode.com>
To: zsh-workers@math.gatech.edu
Subject: Re: Current state of 3.1.2
Date: Wed, 08 Oct 1997 15:43:38 +0100	[thread overview]
Message-ID: <199710081443.KAA27464@math.gatech.edu> (raw)
In-Reply-To: Your message of "Wed, 08 Oct 1997 14:27:24 BST." <199710081327.OAA01042@sgi13.york.ac.uk>

wjf103@york.ac.uk said:
> Does anyone have a 'clean' version of zsh 3.1.2 with all the 
> 'official' patches applied? I have had problems with my email and 
> missed many patches. 

Is there such a thing as an official patch?  This would be really useful, 
though.  Perhaps keep the zsh-RCS.tar.gz up to date, assuming Zoltan has such 
a thing himself?  (With the caveat that sometimes this would be broken, but 
hackers can live with that.)  Or use some kind of distributed CVS setup, as 
some projects are said to do, where a select group has modify access, but the 
rest of us just get to watch; that's probably more effort than it's worth, 
though.

Perhaps there could be some way of archiving just the patches posted to 
zsh-workers, in an order that they could be applied to the latest test 
version? This would typically just involve those sending patches to put an 
indication in the header of their mail ("Subject: PATCH ...", or something), 
with the occasional intervention needed when people supply incompatible 
patches.

zsh-workers is archived, of course, but last time I tried, it was non-trivial 
to find the patches.



  reply	other threads:[~1997-10-08 14:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-10-08 13:27 Wez Furlong
1997-10-08 14:43 ` Bruce Stephens [this message]
1997-10-08 16:46   ` Timothy J Luoma
1997-10-09  5:53     ` Archiving patches (Was: Current state of 3.1.2) Geoff Wing
1997-10-09  9:33       ` Andrew Main
1997-10-09 17:42         ` Timothy J Luoma
1997-10-09 17:34       ` Timothy J Luoma
1997-10-09 17:55         ` Andrew Main
1997-10-09 18:06           ` Timothy J Luoma
1997-10-09 17:48 Current state of 3.1.2 Wez Furlong

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=199710081443.KAA27464@math.gatech.edu \
    --to=b.stephens@isode.com \
    --cc=zsh-workers@math.gatech.edu \
    /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).