From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16854 invoked by alias); 13 Feb 2013 12:16:12 -0000 Mailing-List: contact archer-help@sourceware.org; run by ezmlm Sender: Precedence: bulk List-Post: List-Help: List-Subscribe: List-Id: Received: (qmail 16834 invoked by uid 22791); 13 Feb 2013 12:16:10 -0000 X-SWARE-Spam-Status: No, hits=-6.2 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,KHOP_SPAMHAUS_DROP,RCVD_IN_DNSWL_HI,RCVD_IN_HOSTKARMA_W,RP_MATCHES_RCVD,SPF_HELO_PASS X-Spam-Check-By: sourceware.org Date: Wed, 13 Feb 2013 12:16:00 -0000 From: Jan Kratochvil To: Tom Tromey Cc: Project Archer Subject: Re: Proposal to change branch maintenance Message-ID: <20130213121556.GA21353@host2.jankratochvil.net> References: <874nhipla5.fsf@fleche.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <874nhipla5.fsf@fleche.redhat.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-SW-Source: 2013-q1/txt/msg00002.txt.bz2 On Mon, 11 Feb 2013 22:56:18 +0100, Tom Tromey wrote: > So, new branches would be like "tromey/project" rather than the current > "archer-tromey-project". > > I don't propose renaming existing branches. IMO if there should be a different naming the existing should be renamed, otherwise it is more complicated/mess than it was. > Third, what about adopting a convention for a "README.archer" file in > the top-level of each branch? That would not work for merges of multiple branches. Some ARCHER.branchname would work. But ... > I think newer git even has some automated thing for documenting > branches, but unfortunately I think we aren't all on a new-enough git > yet. We could adopt that when we're ready. ... you probably mean "git branch --edit-description", I do not know it. It exists even in the oldest supported Fedora (F-17) and in reality archer.git is not in use outside of RH so I do not see a problem with --edit-description. Jan