Return-Path: Delivered-To: apmail-buildr-commits-archive@www.apache.org Received: (qmail 48425 invoked from network); 2 Mar 2009 23:50:36 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 2 Mar 2009 23:50:36 -0000 Received: (qmail 90463 invoked by uid 500); 2 Mar 2009 23:50:36 -0000 Delivered-To: apmail-buildr-commits-archive@buildr.apache.org Received: (qmail 90444 invoked by uid 500); 2 Mar 2009 23:50:36 -0000 Mailing-List: contact commits-help@buildr.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@buildr.apache.org Delivered-To: mailing list commits@buildr.apache.org Received: (qmail 90435 invoked by uid 99); 2 Mar 2009 23:50:36 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Mar 2009 15:50:36 -0800 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Mar 2009 23:50:26 +0000 Received: by eris.apache.org (Postfix, from userid 65534) id 027D32388962; Mon, 2 Mar 2009 23:50:06 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r749479 - /buildr/trunk/doc/scripts/buildr-git.rb Date: Mon, 02 Mar 2009 23:50:05 -0000 To: commits@buildr.apache.org From: vborja@apache.org X-Mailer: svnmailer-1.0.8 Message-Id: <20090302235006.027D32388962@eris.apache.org> X-Virus-Checked: Checked by ClamAV on apache.org Author: vborja Date: Mon Mar 2 23:50:05 2009 New Revision: 749479 URL: http://svn.apache.org/viewvc?rev=749479&view=rev Log: Made clear in buildr-git notice that the github mirror is not a replacement for Apache SVN, but just a convenience. Modified: buildr/trunk/doc/scripts/buildr-git.rb Modified: buildr/trunk/doc/scripts/buildr-git.rb URL: http://svn.apache.org/viewvc/buildr/trunk/doc/scripts/buildr-git.rb?rev=749479&r1=749478&r2=749479&view=diff ============================================================================== --- buildr/trunk/doc/scripts/buildr-git.rb (original) +++ buildr/trunk/doc/scripts/buildr-git.rb Mon Mar 2 23:50:05 2009 @@ -110,24 +110,30 @@ THE GITHUB MIRROR: - Buildr has an unofficial git mirror on github, maintained by Victor: + Buildr has an unofficial git mirror on github, maintained by Apache committers: http://github.com/buildr/buildr - Actually it's not Victor who manually updates it, he has a cron-job on his - server, that only runs + This mirror DOES NOT replace Apache's SVN repository. We really care about + using Apache infrastructure and following Apache project guidelines for + contributions. This git mirror is provided only for developers convenience, + allowing them to easily create experimental branches or review code from + other committers. - git synchronize + All code that wants to make it to the official Apache Buildr repository needs + to be committed to the Apache SVN repository by using the command: - A command you also have configured on your .git/config file. + git synchronize - However there are some limitations due to the fact that git-svn cannot - commit as multiple authors (unless all of them provided their passwords - to Victor, yet he doesn't want to take over the world.) - This means that if a commit is pushed to buildr/master and has not - already been pushed by YOU to Apache's SVN by using `git apache-push` - your change will be commited to apache/trunk having Victor as the author - (that's how he gains meritocratic points at Apache :P). + This command will synchronize both ways svn<->git to keep trunk upto date. + You need to be an Apache committer an have permissions on the SVN repo. + + It's VERY IMPORTANT for Buildr committers to remember that contributions from + external entities wanting to be accepted will require them to sign the Apache ICLA. + We provide the git mirror to make it easier for people to experiment and + contribute back to Buildr, before merging their code in, please remember they + have to create create a JIRA issue granting ASF permission to include their code, + just like any other contribution following Apache's guidelines. So, it's very important - if you care about meritocracy - to follow or at least that you get an idea of the recommended workflow.