From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.dk (Zsh hackers list)
Subject: Re: ANNOUNCEMENT: zsh 4.0.1 released
Date: Fri, 1 Jun 2001 18:10:16 +0000 [thread overview]
Message-ID: <1010601181016.ZM20378@candle.brasslantern.com> (raw)
In-Reply-To: <Tc0a88d0153e1c2ba67@mailsweeper01.cambridgesiliconradio.com>
In-Reply-To: <20010601134217.A2408@dman.com>
On Jun 1, 1:42pm, Clint Adams wrote:
}
} On the other hand, there's no pressing need to branch until just before 4.0.2
} is to be released.
Right, 4.0.1 is tagged, so we can always create a branch off that point.
The only ugly part of "branch later" happens if we start adding files
(such as configure.ac ...).
On Jun 1, 6:50pm (really only 8 minutes later), Peter Stephenson wrote:
}
} OK, in that case I've created a branch called `zsh-4_0-patches' (after a
} botched attempt called `zsh-4_0_1-patches', ignore that). We'll have to
} decide patch by patch what is important enough to go on that branch, but
Do you want me to take charge of that, like I've been doing for 3.0?
Or are you OK with it now that it's all in one repository?
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
next prev parent reply other threads:[~2001-06-01 18:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Tc0a88d0153e16b257e@mailsweeper01.cambridgesiliconradio.com>
2001-06-01 16:35 ` Clint Adams
2001-06-01 16:48 ` Peter Stephenson
2001-06-01 17:30 ` Clint Adams
2001-06-01 17:42 ` Clint Adams
2001-06-01 18:10 ` Bart Schaefer [this message]
2001-06-01 18:15 ` Peter Stephenson
2001-06-01 17:50 ` Peter Stephenson
2001-06-01 18:19 ` Andrej Borsenkow
2001-06-01 18:37 ` Peter Stephenson
2001-06-02 13:22 ` Adam Spiers
2001-06-02 14:25 ` Bart Schaefer
2001-06-02 17:42 ` Andrej Borsenkow
2001-06-03 4:16 ` E. Jay Berkenbilt
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=1010601181016.ZM20378@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=zsh-workers@sunsite.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).