From: Tim Cross <theophilusx@gmail.com>
To: "Óscar Fuentes" <ofv@wanadoo.es>
Cc: emacs-devel@gnu.org
Subject: Re: Release tags
Date: Wed, 5 Sep 2012 08:43:19 +1000 [thread overview]
Message-ID: <CAC=50j84CE_=S8fnE6v9XaWz2MKHEbERKDEA8VqAhaFcvfN8Mw@mail.gmail.com> (raw)
In-Reply-To: <87ipbtlk7v.fsf@wanadoo.es>
On 5 September 2012 04:24, Óscar Fuentes <ofv@wanadoo.es> wrote:
> 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. Release tags especially.
>>
>> If there are multiple Emacs 24.2 tags in the repository, how is one
>> supposed to know which is the real Emacs 24.2?
>
> Any of them will do, because the revision (and hence the tag) determines
> the complete state of the source tree.
>
> Plus the complete VC history that precedes that revision. So if the
> emacs-24 branch were magically lost, it could be partially recovered (VC
> history included) from any other branch that contains a merged revision
> that comes from emacs-24. (Partially means "except the revisions
> committed after the emacs-24 revision you have at hand.")
>
>
Just to clarify and get things back on track.
I cannot see any emacs-24.2 tag in the main trunk. I suspect (but
don't know for sure) that this is because the tag was not made in the
emacs-24 branch before it was merged back into trunk. I suspect that
the next merge from the emacs-24 branch will bring the tag into trunk.
I don't see any problem with that.
The reason I wanted the tag is that most of the time I run off the
head of the main trunk. However, sometimes, if the trunk has some
instabiity which is causing me problems, it is useful to have a known
'good state' in the trunk which allows me to check it out in a
convenient way. The tag provides that convenience - I don't have to
look back through the revisions to work out which difficult to
remember revison number corresponds to the last stable release version
Obviously, I could just check out the emacs-24 branch. However, I was
hoping to avoid having to either switch branches or have two separate
working trees - I find it more convenient to just maintain one tree.
An earlier post in this thread identifies the revision number where
the emacs-24.2 version was merged back into the dev trunk, so I can
achieve what I want using that revision number. The tag is a
convenience, but not essential.
Tim
--
Tim Cross
next prev parent reply other threads:[~2012-09-04 22:43 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAC=50j84CE_=S8fnE6v9XaWz2MKHEbERKDEA8VqAhaFcvfN8Mw@mail.gmail.com' \
--to=theophilusx@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=ofv@wanadoo.es \
/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.