Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Apple Message framework v1244.3)
Subject: Re: git commit: davisp - GIT OK
From: Jan Lehnardt <jan@apache.org>
In-Reply-To: 
 <CAJ_m3YDWQUDaja10bxx+ahZNfY1cW=kKOGULVyrLKTdd0suvcQ@mail.gmail.com>
Date: Tue, 23 Aug 2011 12:06:57 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <9820D627-776F-4680-B9A9-A662AB0A566F@apache.org>
References: <20110822034558.AA1D559338@tyr.zones.apache.org>
 <CAJ_m3YDWQUDaja10bxx+ahZNfY1cW=kKOGULVyrLKTdd0suvcQ@mail.gmail.com>
To: dev@couchdb.apache.org

Paul,

great work! I didn't some kicking the tires and reported to you on IRC. =
It looks like this is a thumbs up on my end when the commit-hash thing =
is sorted out.

Thanks again for pushing this, I can't wait.

Cheers
Jan
--=20

On Aug 22, 2011, at 05:55 , Paul Davis wrote:

> Fellow Committers,
>=20
> I've gotten a Git clone of the SVN repository configured to receive
> actual writes. Now for everyone to try writing to it start causing
> mischief.
>=20
> Things that committers should do:
>=20
>    1. Clone the repository
>    2. Edit the AUTHORS file marking their entry with something like =
"GIT OK"
>      so that I know who can write to the repository
>    3. Try and kill the repository
>=20
> For 1, there are instructions here:
>=20
>    http://git-wip-us.apache.org
>=20
> Basically to clone:
>=20
>    $ git clone https://git.apache.org/repos/asf/couchdb.git
>=20
> There are instructions on how to configure a .netrc file on that page
> so you don't have to type your password every time you want to push.
>=20
> For 3, I'd like everyone to start trying to do mean things to this
> repository. Try to rewind trunk or master. The only branches that are
> protected are master, trunk and anything starting with rel/. Try
> pushing commits by people that aren't couchdb committers. Anything you
> can think of. Other things to try are to include UTF-8 data in commit
> messages or in Git committer names and the like.
>=20
> If you get any sort of backtrace when you git push to that repository
> please copy paste the entire command and output and send me an email
> with what you were trying to do with the paste.
>=20
> Until then, happy hunting.
>=20
> On Sun, Aug 21, 2011 at 10:45 PM,  <davisp@apache.org> wrote:
>> Updated Branches:
>>  refs/heads/master 79c82c3d3 -> 2698e68c5
>>=20
>>=20
>> davisp - GIT OK
>>=20
>>=20
>> Project: http://git-wip-us.apache.org/repos/asf/couchdb/repo
>> Commit: =
http://git-wip-us.apache.org/repos/asf/couchdb/commit/2698e68c
>> Tree: http://git-wip-us.apache.org/repos/asf/couchdb/tree/2698e68c
>> Diff: http://git-wip-us.apache.org/repos/asf/couchdb/diff/2698e68c
>>=20
>> Branch: refs/heads/master
>> Commit: 2698e68c5555ff888915a1f9c11bdeb22f06e884
>> Parents: 79c82c3
>> Author: Paul J. Davis <davisp@apache.org>
>> Authored: Sun Aug 21 22:43:31 2011 -0500
>> Committer: Paul J. Davis <davisp@apache.org>
>> Committed: Sun Aug 21 22:43:31 2011 -0500
>>=20
>> =
----------------------------------------------------------------------
>>  AUTHORS |    2 +-
>>  1 files changed, 1 insertions(+), 1 deletions(-)
>> =
----------------------------------------------------------------------
>>=20
>>=20
>> http://git-wip-us.apache.org/repos/asf/couchdb/blob/2698e68c/AUTHORS
>> =
----------------------------------------------------------------------
>> diff --git a/AUTHORS b/AUTHORS
>> index 16a926c..f057a1d 100644
>> --- a/AUTHORS
>> +++ b/AUTHORS
>> @@ -9,7 +9,7 @@ documentation or developing software. Some of these =
people are:
>>  * Noah Slater <nslater@apache.org>
>>  * Christopher Lenz <cmlenz@apache.org>
>>  * J. Chris Anderson <jchris@apache.org>
>> - * Paul Joseph Davis <davisp@apache.org>
>> + * Paul Joseph Davis <davisp@apache.org>    GIT OK
>>  * Adam Kocoloski <kocolosk@apache.org>
>>  * Jason Davies <jasondavies@apache.org>
>>  * Mark Hammond <mhammond@skippinet.com.au>
>>=20
>>=20