From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: guile-devel@gnu.org
Subject: Re: [Guile-commits] GNU Guile branch, wip-1-8-mingw-build, updated. release_1-8-7-22-g7edad77
Date: Fri, 26 Mar 2010 14:37:02 +0100 [thread overview]
Message-ID: <87y6hfgq69.fsf@ambire.localdomain> (raw)
In-Reply-To: <m3aatvs2v7.fsf@pobox.com> (Andy Wingo's message of "Fri, 26 Mar 2010 13:07:24 +0100")
() Andy Wingo <wingo@pobox.com>
() Fri, 26 Mar 2010 13:07:24 +0100
On Fri 26 Mar 2010 01:31, Neil Jerram <neil@ossau.uklinux.net> writes:
> Is there a nice way of marking a branch as obsolete/historical, or of
> adding an explanatory note to it?
I don't know. It would only be for purposes of gitweb/cgit, I don't
think git has this concept.
Perhaps "git tag" with some kind of conventional prefix? E.g.,
$ { date -u +"%F %T UTC" ; echo ; } > TMP
$ cat >>TMP <<EOF
This branch is live|dead|zombified|historic|pickled|putrescent|etc.
We keep it around because <explanation>.
If you delete it, someone might complain.
If you add to it, you probably are confused.
EOF
$ git tag -F TMP BRANCH-NAME-nb
This way one can easily ignore *-nb tags. Using a suffix ensures
that the tag hierarchy mirrors the branch hierarchy (if any).
thi
next prev parent reply other threads:[~2010-03-26 13:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1NnhBU-0002dm-1u@vcs-noshell.in.savannah.gnu.org>
2010-03-06 22:22 ` [Guile-commits] GNU Guile branch, wip-1-8-mingw-build, updated. release_1-8-7-22-g7edad77 Ludovic Courtès
2010-03-07 22:30 ` Neil Jerram
2010-03-26 0:31 ` Neil Jerram
2010-03-26 12:07 ` Andy Wingo
2010-03-26 13:37 ` Thien-Thi Nguyen [this message]
2010-03-26 22:42 ` Neil Jerram
2010-03-26 22:17 ` Neil Jerram
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y6hfgq69.fsf@ambire.localdomain \
--to=ttn@gnuvola.org \
--cc=guile-devel@gnu.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).