From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17763 invoked by alias); 17 Dec 2012 10:14:10 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 30902 Received: (qmail 4087 invoked from network); 17 Dec 2012 10:14:06 -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=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE, SPF_HELO_PASS autolearn=ham version=3.3.2 Received-SPF: none (ns1.primenet.com.au: domain at bewatermyfriend.org does not designate permitted sender hosts) From: Frank Terbeck To: zsh-workers@zsh.org Subject: Re: PATCH: document git in Etc/zsh-development-guide In-Reply-To: <20121217085215.GA87227@redoubt.spodhuis.org> (Phil Pennock's message of "Mon, 17 Dec 2012 03:52:15 -0500") References: <20121217085215.GA87227@redoubt.spodhuis.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) Date: Mon, 17 Dec 2012 10:59:23 +0100 Message-ID: <878v8xt2x0.fsf@ft.bewatermyfriend.org> MIME-Version: 1.0 Content-Type: text/plain X-Df-Sender: [pbs]MDExNTM1 Phil Pennock wrote: > Note that http://www.zsh.org/ appears to be down, and zsh.sunsite.dk > does not exist in DNS, but in searching for the "Zsh Patch Archive", I > can only find a reference to: > http://zsh.sunsite.dk/Patches/ All sunsite.dk links are invalid and should point to sf.net instead: http://zsh.sourceforge.net/Patches/ > The development guide still says to prefix patch mails with "PATCH:" for > the patches to make it into the patch archive. Is this still true, and > if so where is the archive? Or should I also change that text to permit > "[PATCH]" and "[PATCH n/m]" per git-format-patch? That would be good. > +Use of Git > +---------- > + > +zsh has migrated from CVS to git for version control. We have so far > +kept our workflow unchanged; to wit: > + > + 1. change is developed and posted to the zsh-workers mailing list > + 2. the zsh-workers list management software adds an X-Seq: header > + 3. an entry is added to ChangeLog with details, including the X-Seq: > + header. > + [Open Question: should the first 6 or so characters of the commit > + fingerprint be included, so: "* 12345/deadbeef: frobbed the baz" ?] How about generating the ChangeLog before releases instead of updating it manually? I find that to be an unnecessary manual step, especially since the same information is just one "git log" or "gitk" away. I wrote a generation tool a while back, which I linked to a couple of times already[1]. If I am the only one who thinks that this might be useful, please tell me, so I can keep my mouth shut about it in the future. :-) Regards, Frank [1] http://ft.bewatermyfriend.org/comp/genchangelog.html