unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jason Rumney <jasonr@gnu.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: "Óscar Fuentes" <ofv@wanadoo.es>, emacs-devel@gnu.org
Subject: Re: Release tags
Date: Wed, 05 Sep 2012 22:55:52 +0800	[thread overview]
Message-ID: <87r4qga58n.fsf@gnu.org> (raw)
In-Reply-To: <m2d321n0iq.fsf@igel.home> (Andreas Schwab's message of "Tue, 04 Sep 2012 19:47:09 +0200")

Andreas Schwab <schwab@linux-m68k.org> writes:

> Jason Rumney <jasonr@gnu.org> writes:
>
>> No use of a tag that I have ever seen was for a revision. It was for the
>> state of the source tree at that point in time.
>
> A revision _is_ a state of the tree at one point in time.

Except when you merge that revision onto another branch, some here
seemed to be saying the tag would be merged with it, which makes no
sense to me, because after the merge what gets checked in should be a
different revision (even though the patch from the previous revision to
the new one is the same between branches, the content of the tree is
different).




  reply	other threads:[~2012-09-05 14:55 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-28 16:48 Release tags chad
2012-08-29  2:40 ` Chong Yidong
2012-09-04  0:40   ` Tim Cross
2012-09-04  2:25     ` Óscar Fuentes
2012-09-04  2:29     ` William Stevenson
2012-09-04  2:50       ` Eli Zaretskii
2012-09-04 14:32         ` Jason Rumney
2012-09-04 15:57           ` Óscar Fuentes
2012-09-04 16:04             ` Jason Rumney
2012-09-04 17:47               ` Andreas Schwab
2012-09-05 14:55                 ` Jason Rumney [this message]
2012-09-05 15:18                   ` Andreas Schwab
2012-09-05 15:33                     ` Óscar Fuentes
2012-09-07 13:22                       ` Jason Rumney
2012-09-07 14:35                         ` Eli Zaretskii
2012-09-07 15:27                         ` Stefan Monnier
2012-09-04 18:24               ` Óscar Fuentes
2012-09-04 22:43                 ` Tim Cross
2012-09-05  1:53                   ` Stephen J. Turnbull
2012-09-05  2:34                   ` Óscar Fuentes
2012-09-05  3:07                     ` Stephen J. Turnbull
2012-09-05  3:49                       ` Óscar Fuentes
2012-09-05  5:11                         ` Stephen J. Turnbull
2012-09-05  6:34                           ` Jambunathan K
2012-09-05 12:48                           ` Tim Cross
2012-09-05 16:25                           ` Eli Zaretskii
2012-09-05 16:23                         ` Eli Zaretskii
2012-09-05 16:21                       ` Eli Zaretskii
2012-09-05 17:32                         ` Stephen J. Turnbull
2012-09-05 17:42                           ` Eli Zaretskii
2012-09-05 14:32                     ` Stefan Monnier
2012-09-04 16:57             ` Eli Zaretskii
2012-09-04 16:53           ` Eli Zaretskii
2012-09-05  7:16         ` Glenn Morris

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=87r4qga58n.fsf@gnu.org \
    --to=jasonr@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=ofv@wanadoo.es \
    --cc=schwab@linux-m68k.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 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).