X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=mail.ud03.udmedia.de; h= subject:to:references:from:message-id:date:mime-version :in-reply-to:content-type:content-transfer-encoding; s=beta; bh= jcFK6Cnc5swAgHNoCDf+VT9jrSzwM2DnQpnyVTg0hrY=; b=UnIl69V6MTj0aZru TCZ1pPsR15CrbItjzNfM93WulPBc0li4msgnZ23Fr0evJh5A96m8VUeOoW3r8KGX 5+LcNhee8NH5UAzX+X8YijanUpMOp9lJXgSobbRHf9yNObFJ5vfaulX7GMBm61Jj 8Z8vrZaIraQl+JfdqqYmDuKrmvk= Subject: Re: [geda-user] community repository To: geda-user AT delorie DOT com References: <55E6DBB1 DOT 5080704 AT jump-ing DOT de> From: "Markus Hitter (mah AT jump-ing DOT de) [via geda-user AT delorie DOT com]" Message-ID: <55E83275.6000701@jump-ing.de> Date: Thu, 3 Sep 2015 13:43:49 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: <55E6DBB1.5080704@jump-ing.de> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit 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 Precedence: bulk Fine. Seeing some 90% agreement I implemented this as described for the pcb repo today. Also made the email sending robot to include an URL to the commit, which resulted in some noise on the -commit list. Now developers can - Create, modify, rebase as many branches as they see use for, as long as the branch name starts with 'home/', followed by the user name, followed by another '/', followed by the actual branch name. An example for me is branch home/traumflug/getopt (note: no leading / ) http://git.geda-project.org/pcb/log/?h=home/traumflug/getopt - Create, modify, rebase bug tracking branches. Bug tracking branches are also identified by their name, start with uppercase 'LP', followed by the bug number in Launchpad, optionally followed by more text. Example: http://git.geda-project.org/pcb/log/?h=LP699471 - Moderately experienced developers (currently that's all developers) can also push to master, but not modify master. Once pushed, these commits are kept, so make sure to at least run a 'make check' before pushing. To become a developer, simply send your SSH public key to DJ Delorie or me. Happy hacking, Markus -- - - - - - - - - - - - - - - - - - - - Dipl. Ing. (FH) Markus Hitter http://www.jump-ing.de/