X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	dj AT delorie DOT com
X-Recipient:	geda-user AT delorie DOT com
X-Spam-Checker-Version:	SpamAssassin 3.3.1 (2010-03-16) on mail.theimps.com
X-Spam-Level:
X-Spam-Status:	No, score=-100.0 required=5.0 tests=ALL_TRUSTED,SHORTCIRCUIT
	shortcircuit=ham autolearn=disabled version=3.3.1
From:	Peter TB Brett <peter AT peter-b DOT co DOT uk>
To:	Markus Hitter <mah AT jump-ing DOT de>
Cc:	DJ Delorie <dj AT delorie DOT com>, geda-user AT delorie DOT com,
	geda-developers AT lists DOT launchpad DOT net
Subject:	[geda-user] Re: [Geda-developers] git.geda-project.org permissions change
References:	<87fvtffapt DOT fsf AT harrington DOT peter-b DOT co DOT uk>
	<BEA3A8DC-904B-4C5A-A357-8867F94D2C05 AT jump-ing DOT de>
	<201309082104 DOT r88L4Rx2003804 AT envy DOT delorie DOT com>
	<522CE8ED DOT 2040200 AT jump-ing DOT de>
Date:	Sun, 08 Sep 2013 22:51:24 +0100
In-Reply-To:	<522CE8ED.2040200@jump-ing.de> (Markus Hitter's message of "Sun,
	08 Sep 2013 23:15:25 +0200")
Message-ID:	<87vc2baso3.fsf@harrington.peter-b.co.uk>
User-Agent:	Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux)
MIME-Version:	1.0
Reply-To:	geda-user AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	geda-user AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

--=-=-=
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

Markus Hitter <mah AT jump-ing DOT de> writes:

> Am 08.09.2013 23:04, schrieb DJ Delorie:
>> I defer to Peter's git expertise in setting up the git stuff.  If our
>> previous practices were dangerous, we need to change them, despite any
>> "convenience" of being able to work around the system's intended use.
>
> To date I still wait for somebody showing me an incident where harm
> actually happened. Instead, Peter told us he actually uses exactly the
> workflow I use myself, outlined a week ago, and is used by many other
> projects, too. So much to his "expertise".

Maybe there was a breakdown in communication somewhere (maybe my e-mails
were not getting through or perhaps my English was not clear enough),
but I'm sure that I explained, with examples, how methods that work well
in a personal repository (that only a single developer commits to) often
are not appropriate for a repository that multiple developers
collaborate in.

stgit is a good example of a tool that I find ideal for personal
repositories, but I would never in a million years use it on a
repository that other people might commit to.

I apologise for misleading you, if you interpreted me differently.

                                    Peter

=2D-=20
Dr Peter Brett <peter AT peter-b DOT co DOT uk>

--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)

iEYEARECAAYFAlIs8VwACgkQZ7Gbq7g7vpr/TQCdFJtPGVywWl+3Ds6fzleJcVWW
M8EAmgMM7dwtJLpVWf4npi0Y4Q26FA5I
=OF8W
-----END PGP SIGNATURE-----
--=-=-=--

- Raw text -