zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <p.stephenson@samsung.com>
To: Phil Pennock <zsh-workers+phil.pennock@spodhuis.org>,
	zsh-workers@zsh.org
Subject: Re: PATCH: document git in Etc/zsh-development-guide
Date: Tue, 18 Dec 2012 16:46:28 +0000	[thread overview]
Message-ID: <20121218164628.0d0196e5@pwslap01u.europe.root.pri> (raw)
In-Reply-To: <20121218093618.GB11509@redoubt.spodhuis.org>

On Tue, 18 Dec 2012 04:36:18 -0500
Phil Pennock <zsh-workers+phil.pennock@spodhuis.org> wrote:
> I pushed the changes to CVS after making them, figuring that Peter is
> working from a fixed point for the 5.0.1 candidates and can either
> branch zsh-development-guide if we wants to elide my changes, or keep
> the content, because my understanding is that after 5.0.1 goes out,
> we'll be on git, so guidance on how to contribute "as of release
> 5.0.1" will require git.

There's no branch --- it's a waste of time unless people are actively
developing during the release --- but presumably the latter is true.

pws


  reply	other threads:[~2012-12-18 16:56 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-17  8:52 Phil Pennock
2012-12-17  9:59 ` Frank Terbeck
2012-12-17 11:22   ` Phil Pennock
2012-12-17 10:15 ` Peter Stephenson
2012-12-17 11:00   ` Phil Pennock
2012-12-17 13:50     ` Oliver Kiddle
2012-12-18  9:36       ` Phil Pennock
2012-12-18 16:46         ` Peter Stephenson [this message]
2012-12-19 14:06         ` Oliver Kiddle
2012-12-20  9:57           ` Phil Pennock
2012-12-20 13:38             ` Oliver Kiddle
2012-12-20 13:55               ` Peter Stephenson
2012-12-20 15:55               ` Bart Schaefer
2012-12-20 18:42                 ` Peter Stephenson
2012-12-20 20:58               ` Phil Pennock
2012-12-17 14:17   ` Benjamin R. Haskell
2012-12-18  9:33     ` Phil Pennock
2012-12-18 14:11       ` Benjamin R. Haskell
2012-12-18 20:37         ` zsh.org & patch archive Phil Pennock
2012-12-19  6:49           ` 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=20121218164628.0d0196e5@pwslap01u.europe.root.pri \
    --to=p.stephenson@samsung.com \
    --cc=zsh-workers+phil.pennock@spodhuis.org \
    --cc=zsh-workers@zsh.org \
    /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).