From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14355 invoked by alias); 17 Dec 2012 11:22:21 -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: 30905 Received: (qmail 6571 invoked from network); 17 Dec 2012 11:22:07 -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=-3.3 required=5.0 tests=BAYES_00,DKIM_ADSP_ALL, DKIM_SIGNED,RCVD_IN_DNSWL_MED,T_DKIM_INVALID,UNPARSEABLE_RELAY autolearn=ham version=3.3.2 Received-SPF: none (ns1.primenet.com.au: domain at spodhuis.org does not designate permitted sender hosts) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=spodhuis.org; s=d201210; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID:Subject:To:From:Date; bh=2KmVzpIye04SrL1wvw+wY4F+DkKRJnndfg7XgXq0X2c=; b=uxidtBubIXwKhMV1sKLE4/VbjpoccCTkN+1sEB5K7AodvU/kY+OPlljvifBt8qFiZ3I7370JWqp9Ui5Y+6Y2HVNd8QR7ACnvrOsdqOLpstrHhqzRvTu4hWCUgwnGKnWdV/IOdPFRCz57p6OiQIcIgnQ1QuBdq+tBt0rtVbBVLVM=; Date: Mon, 17 Dec 2012 06:22:02 -0500 From: Phil Pennock To: zsh-workers@zsh.org Subject: Re: PATCH: document git in Etc/zsh-development-guide Message-ID: <20121217112202.GB89579@redoubt.spodhuis.org> Mail-Followup-To: zsh-workers@zsh.org References: <20121217085215.GA87227@redoubt.spodhuis.org> <878v8xt2x0.fsf@ft.bewatermyfriend.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <878v8xt2x0.fsf@ft.bewatermyfriend.org> On 2012-12-17 at 10:59 +0100, Frank Terbeck wrote: > All sunsite.dk links are invalid and should point to sf.net instead: > > http://zsh.sourceforge.net/Patches/ Thanks. > How about generating the ChangeLog before releases instead of updating > it manually? My understanding from the previous thread is that we're taking small steps to make the transition manageable. Notably, neither of the two most prolific contributors to zsh (Peter and Bart) uses Git yet. So we do things the same way they are now. Once all the developers have gotten a good feel for how things work with git and have internalised the new tooling's model, _then_ we might reconsider changes to the workflow. For now, we let the tooling support the model that is working. Peter, Bart: I was in much the same situation as you are now, when Exim switched. At the time, my stance was "I don't care which VCS is used, I don't think changing VCS solves any fundamental issues with contribution, I didn't care, but now is a good time to consider our options" (it was an in-person meetup of the maintainers). A couple of people were strongly pro-git, so we went along with that. I then spent the next couple of months swearing. There was mutual support on the mailing-lists as we grappled with the changes. Our wiki gained a couple of entries from various folks: http://wiki.exim.org/EximGit http://wiki.exim.org/SampleWorkFlow The one thing I'll say now: % git config --global user.name "Fred Bloggs" % git config --global user.email fred@examle.org because git commits are immutable once published and you probably want to get the correct name and address for publication set up. You can vary these on a per-repo basis too. -Phil