zsh-workers
 help / color / mirror / code / Atom feed
From: Bruce Stephens <B.Stephens@isode.com>
To: zsh-workers@math.gatech.edu
Subject: Re: patch archive set up
Date: Fri, 10 Oct 1997 10:33:43 +0100	[thread overview]
Message-ID: <199710100933.FAA19060@math.gatech.edu> (raw)
In-Reply-To: Your message of "Thu, 09 Oct 1997 21:13:19 EDT." <199710100113.VAA10505@luomat.peak.org>


luomat+zsh+users@luomat.peak.org said:
> for example:

> PATCH: 3.0.4 Src/subst.c 

I agree with Geoff Wing, a description is more sensible, since source changes 
often have (or should have!) associated documentation changes, at least.

I'd like the archive to be semi-automatically appliable, so I'd like to be 
able to grab the most recent zsh from the archive, grab all the patches 
(filtering on the version number), and run a zsh script to apply them all.  So 
as a start, I'd suggest that all patches ought to be taken at the top source 
level (so I'd do "cd zsh-3.1.2; patch -p0 < ..."), and that mails would 
contain either the actual patch, or a gzipped/compressed patch, but not tarred 
stuff, because that's more fiddly to process.

I must admit, I'd prefer just a patched version to be made available, say once 
a week or something.  Does anybody keep a zsh suitably patched?

My reason is that normally I haven't been patching zsh, but just recently 
there have been a couple of useful patches that I wanted, so I was forced to 
try to get up to date enough to apply them, and it wasn't trivial!  In fact, I 
eventually couldn't apply them cleanly, but I got what I wanted and still have 
a working zsh.



  parent reply	other threads:[~1997-10-10  9:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-10-10  1:13 Timothy J Luoma
1997-10-10  8:50 ` Geoff Wing
1997-10-10  8:54 ` Andrew Main
1997-10-10  9:33 ` Bruce Stephens [this message]
1997-10-13 12:16 ` Andrej Borsenkow
1997-10-15  0:59   ` Timothy J Luoma

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=199710100933.FAA19060@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).