From: "Eric S. Raymond" <esr@thyrsus.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Tag cleanup
Date: Thu, 9 Jan 2014 06:24:07 -0500 [thread overview]
Message-ID: <20140109112407.GA4818@thyrsus.com> (raw)
In-Reply-To: <83a9f5ej2b.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org>:
> I think everything except EMACS_PRETEST_* and emacs-xx.yy (why the
> different letter-case and syntax, btw?) should be removed.
The tags beginning eith uppercase EMACS and containing _ where you would
expect . are inherited CVS tags; . was not a legal tag character in CVS.
After the switchover to bzr, whover was making release tags (probably Stefan)
started using the more natural emacs-xx.yy convention, but did not rename
the old tags.
I renamed the old CVS-style release tags to corresponding emacs-xx.yy
tags because my philosophy about conversions is to use the idioms of the
target VCS wherever possible, making the join between older and newer
portions of the history invisible.
I didn't rename the *PRETEST* tags because I wasn't sure we'd keep them.
I agree with you that if we keep them they would be better renamed
something like emacs-pretest-xx.yy.zz.
> Those
> other tags are of no importance once the corresponding features have
> landed on mainline. For example, emacs-bidi-base can certainly go.
The *-base tags are almost certainly automatically generated CVS
artifacts that can be removed, but I am conservative by habit in
making such changes.
> But please wait for the "owners" of those other tags to speak up, I
> don't want to usurp anyone's tags.
I don't either.
> The fate of the pretest tags depends on whether we will continue using
> such tags in the future. Emacs pretests are normally quite long, so a
> pretest emacs-24.3.90 is very similar to a released version, and the
> number of commits between it and the next pretest will generally be
> very large. So, if the git experts say that "git describe" and its
> middle field are important, I'd rather see there a small enough number
> than something of 6 digits.
We have two policy questions:
1. Continue using pretest tags? If so, I will rename as you suggest.
If not, I will delete them. I have no strong preference here.
2. What form do we intend to use for the value of
emacs-repository-version? The choices are raw SHA1 or git describe
format; others are theoretically possible but it is normal git
practice to choose one of those two. I advocate the latter as I think
the format is more informative to humans.
These are not my decisions to make unless everybody yawns and says
"don't care". I would much prefer to see a list consensus or, failing
that, maintainer fiat.
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
next prev parent reply other threads:[~2014-01-09 11:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-09 5:37 Tag cleanup Eric S. Raymond
2014-01-09 7:00 ` Eli Zaretskii
2014-01-09 8:13 ` Thien-Thi Nguyen
2014-01-09 11:24 ` Eric S. Raymond [this message]
2014-01-09 13:33 ` Ulrich Mueller
2014-01-09 13:49 ` Eric S. Raymond
2014-01-09 8:44 ` Yuri Khan
2014-01-09 11:26 ` Eric S. Raymond
2014-01-09 16:58 ` Glenn Morris
2014-01-09 17:00 ` Glenn Morris
-- strict thread matches above, loose matches on Subject: below --
2014-01-10 20:06 Eric S. Raymond
2014-01-10 20:23 ` Eli Zaretskii
2014-01-10 21:36 ` Andreas Schwab
2014-01-10 21:41 ` Eric S. Raymond
2014-01-10 22:09 ` Andreas Schwab
2014-01-11 19:40 ` Alan Mackenzie
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=20140109112407.GA4818@thyrsus.com \
--to=esr@thyrsus.com \
--cc=eliz@gnu.org \
--cc=emacs-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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.