unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: esr@thyrsus.com (Eric S. Raymond)
Cc: emacs-devel@gnu.org
Subject: Re: Tag cleanup
Date: Thu, 09 Jan 2014 09:00:12 +0200	[thread overview]
Message-ID: <83a9f5ej2b.fsf@gnu.org> (raw)
In-Reply-To: <20140109053729.E9DC43805F2@snark.thyrsus.com>

> From: esr@thyrsus.com (Eric S. Raymond)
> Date: Thu,  9 Jan 2014 00:37:29 -0500 (EST)
> 
> Please examine this list of tag names,  I want to know which should 
> be thrown out to reduce clutter.

I think everything except EMACS_PRETEST_* and emacs-xx.yy (why the
different letter-case and syntax, btw?) should be removed.  Those
other tags are of no importance once the corresponding features have
landed on mainline.  For example, emacs-bidi-base can certainly go.

But please wait for the "owners" of those other tags to speak up, I
don't want to usurp anyone's tags.

> The question is what out of the remainder is dispensable clutter.
> The *PRETEST* labels seem like obvious candates

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.

If we leave those pretest tags (I think we should), then they are
better renamed to something like emacs-pretest-xx.yy.zz.



  reply	other threads:[~2014-01-09  7:00 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 [this message]
2014-01-09  8:13   ` Thien-Thi Nguyen
2014-01-09 11:24   ` Eric S. Raymond
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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=83a9f5ej2b.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=esr@thyrsus.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).