From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4760 invoked by alias); 22 Feb 2013 21:27:35 -0000 Mailing-List: contact archer-help@sourceware.org; run by ezmlm Sender: Precedence: bulk List-Post: List-Help: List-Subscribe: List-Id: Received: (qmail 4749 invoked by uid 22791); 22 Feb 2013 21:27:34 -0000 X-SWARE-Spam-Status: No, hits=-6.7 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 From: Tom Tromey To: Project Archer Subject: Re: Proposal to change branch maintenance References: <874nhipla5.fsf@fleche.redhat.com> Date: Fri, 22 Feb 2013 21:27:00 -0000 In-Reply-To: <874nhipla5.fsf@fleche.redhat.com> (Tom Tromey's message of "Mon, 11 Feb 2013 14:56:18 -0700") Message-ID: <87d2vs6nur.fsf@fleche.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.2.92 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-SW-Source: 2013-q1/txt/msg00017.txt.bz2 >>>>> "Tom" == Tom Tromey writes: Tom> Third, what about adopting a convention for a "README.archer" file in Tom> the top-level of each branch? This file would explain the branch's Tom> purpose and would let us bypass the tedious step of updating the wiki Tom> whenever pushing a new branch. I've added this to a couple of my branches. You can see it in action with git show origin/archer-tromey-python-checker:README.archer I'd like everyone to add a file like this to their live branches. Don't bother with the dead branches, I'm going to zap them all soon. It is fine with me if you want to wait for the great branch renaming before doing this. thanks, Tom