From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16703 invoked by alias); 11 Feb 2013 21:56:25 -0000 Mailing-List: contact archer-help@sourceware.org; run by ezmlm Sender: Precedence: bulk List-Post: List-Help: List-Subscribe: List-Id: Received: (qmail 16692 invoked by uid 22791); 11 Feb 2013 21:56:25 -0000 X-SWARE-Spam-Status: No, hits=-6.4 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: Proposal to change branch maintenance Date: Mon, 11 Feb 2013 21:56:00 -0000 Message-ID: <874nhipla5.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/msg00000.txt.bz2 I've been thinking a bit about how we maintain branches in archer.git and I'd like to propose a few changes. Let me know what you think. First, going back to something Jan proposed years ago, I think we ought to delete truly dead branches. That is, if a branch has been merged upstream and is no longer useful, let's just zap it. Second, let's change our naming approach for new branches. At the start of the project I was largely ignorant of git, so I made some obvious-in-retrospect mistakes here. I think we should adopt the more git-like "/" separator, and drop the "archer" prefix, as it is redundant given the repository. So, new branches would be like "tromey/project" rather than the current "archer-tromey-project". I don't propose renaming existing branches. Third, what about adopting a convention for a "README.archer" file in the top-level of each branch? This file would explain the branch's purpose and would let us bypass the tedious step of updating the wiki whenever pushing a new branch. 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. Tom