From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-30921-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 16933 invoked by alias); 20 Dec 2012 13:55:41 -0000
Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Workers List <zsh-workers.zsh.org>
List-Post: <mailto:zsh-workers@zsh.org>
List-Help: <mailto:zsh-workers-help@zsh.org>
X-Seq: 30921
Received: (qmail 423 invoked from network); 20 Dec 2012 13:55:29 -0000
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_HI,
	SPF_HELO_PASS autolearn=ham version=3.3.2
Received-SPF: none (ns1.primenet.com.au: domain at samsung.com does not designate permitted sender hosts)
X-AuditID: cbfec7f5-b7fd76d000007247-4d-50d318cd2570
Date: Thu, 20 Dec 2012 13:55:25 +0000
From: Peter Stephenson <p.stephenson@samsung.com>
To: zsh-workers@zsh.org
Subject: Re: PATCH: document git in Etc/zsh-development-guide
Message-id: <20121220135525.33fe9568@pwslap01u.europe.root.pri>
In-reply-to: <22690.1356010707@thecus.kiddle.eu>
References: <20121217085215.GA87227@redoubt.spodhuis.org>
 <20121217101536.6825d808@pwslap01u.europe.root.pri>
 <20121217110035.GA89579@redoubt.spodhuis.org>
 <9514.1355752226@thecus.kiddle.eu>
 <20121218093618.GB11509@redoubt.spodhuis.org>
 <18174.1355925977@thecus.kiddle.eu>
 <20121220095731.GA20954@redoubt.spodhuis.org>
 <22690.1356010707@thecus.kiddle.eu>
Organization: Samsung Cambridge Solution Centre
X-Mailer: Claws Mail 3.7.9 (GTK+ 2.22.0; i386-redhat-linux-gnu)
MIME-version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7bit
X-Brightmail-Tracker:
 H4sIAAAAAAAAA+NgFupiluLIzCtJLcpLzFFi42I5/e/4Nd1zEpcDDDbyWhxsfsjkwOix6uAH
	pgDGKC6blNSczLLUIn27BK6MtR/OMxZcYK2Y2svVwLifpYuRk0NCwETi6YXbTBC2mMSFe+vZ
	uhi5OIQEljJKHPp2lxXCWc4ksXnzVsYuRg4OFgFVifsTNUEa2AQMJaZums0IYosIiEucXXse
	bKiwgK3EzuUQC3gF7CV6T5wAW8ApYCBx7m4bWFxI4AOTxK0uMRCbX0Bf4urfT1BH2EvMvHKG
	EaJXUOLH5Htg9cwCWhKbtzWxQtjyEpvXvGWewCgwC0nZLCRls5CULWBkXsUomlqaXFCclJ5r
	pFecmFtcmpeul5yfu4kREn5fdzAuPWZ1iFGAg1GJh3fhtEsBQqyJZcWVuYcYJTiYlUR4H/wG
	CvGmJFZWpRblxxeV5qQWH2Jk4uCUamDcUZO+91B+W/bVJYKcuQLKjdv6LF7vucd+OCBgt9ie
	dVyyZq4F958kv7o9r3tmTaiwyw4jqXNSxbwej4IEbl360ec7Rbtq+TGBNp1DJ9ptrrIvLTGu
	MA3pLj/3Qz5gxnXPzkOy89gU183qTpCurTgn0j/xNFdE7GyvL2KxR3U6Lh2N4pPRDldiKc5I
	NNRiLipOBAB0321jHQIAAA==

On Thu, 20 Dec 2012 14:38:27 +0100
Oliver Kiddle <okiddle@yahoo.co.uk> wrote:
> > You skipped the commit numbers; my understanding of the simple
> > process to date is that the code change is one commit, the
> > changelog and integration is a second commit, see step 4.  Yes,
> > it's an extra commit,
> 
> My understanding was that ChangeLog files would be handled by Peter
> running Frank Terbeck's script at suitable times such as before a
> release. See workers/30119.

We might do that at some stage, once we're convinced we're not losing
anything (I haven't properly been keeping track of Bart's comments), but
to begin with we'll keep the ChangeLog so everything isn't all changing
at once.

pws