From: Tom Tromey <tromey@redhat.com>
To: Project Archer <archer@sourceware.org>
Subject: Proposal to change branch maintenance
Date: Mon, 11 Feb 2013 21:56:00 -0000 [thread overview]
Message-ID: <874nhipla5.fsf@fleche.redhat.com> (raw)
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
next reply other threads:[~2013-02-11 21:56 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-11 21:56 Tom Tromey [this message]
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
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=874nhipla5.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).