public inbox for archer@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Project Archer <archer@sourceware.org>
Subject: Re: Proposal to change branch maintenance
Date: Fri, 22 Feb 2013 21:27:00 -0000	[thread overview]
Message-ID: <87d2vs6nur.fsf@fleche.redhat.com> (raw)
In-Reply-To: <874nhipla5.fsf@fleche.redhat.com> (Tom Tromey's message of "Mon, 11 Feb 2013 14:56:18 -0700")

>>>>> "Tom" == Tom Tromey <tromey@redhat.com> 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

      parent reply	other threads:[~2013-02-22 21:27 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-11 21:56 Tom Tromey
2013-02-13 11:32 ` Gary Benson
2013-02-13 12:16 ` Jan Kratochvil
2013-02-13 12:33   ` Pedro Alves
2013-02-13 12:53   ` Gary Benson
2013-02-18 16:10   ` Tom Tromey
2013-02-18 16:20     ` Jan Kratochvil
2013-02-18 16:29       ` Tom Tromey
2013-02-18 17:03         ` Jan Kratochvil
2013-02-18 17:40           ` Tom Tromey
2013-02-18 22:01           ` Tom Tromey
2013-02-22 15:54             ` Tom Tromey
2013-02-26 17:33     ` Tom Tromey
2013-02-26 20:13       ` Tom Tromey
2013-02-26 20:31         ` Sergio Durigan Junior
2013-02-27 20:50           ` Tom Tromey
2013-02-27 20:50         ` Tom Tromey
2013-02-27 21:15           ` Tom Tromey
2013-02-18 11:46 ` Sergio Durigan Junior
2013-02-18 16:11   ` Tom Tromey
2013-02-18 16:16     ` Jan Kratochvil
2013-02-22 15:06       ` Tom Tromey
2013-02-22 21:27 ` Tom Tromey [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87d2vs6nur.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=archer@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).