From: Phil Pennock <zsh-workers+phil.pennock@spodhuis.org>
To: zsh-workers@zsh.org
Subject: Re: PATCH: document git in Etc/zsh-development-guide
Date: Mon, 17 Dec 2012 06:22:02 -0500 [thread overview]
Message-ID: <20121217112202.GB89579@redoubt.spodhuis.org> (raw)
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
next prev parent reply other threads:[~2012-12-17 11:22 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 [this message]
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
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=20121217112202.GB89579@redoubt.spodhuis.org \
--to=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).