From: "Óscar Fuentes" <ofv@wanadoo.es>
To: Tim Cross <theophilusx@gmail.com>
Cc: "Óscar Fuentes" <ofv@wanadoo.es>, emacs-devel@gnu.org
Subject: Re: Release tags
Date: Wed, 05 Sep 2012 04:34:41 +0200 [thread overview]
Message-ID: <874nndkxj2.fsf@wanadoo.es> (raw)
In-Reply-To: <CAC=50j84CE_=S8fnE6v9XaWz2MKHEbERKDEA8VqAhaFcvfN8Mw@mail.gmail.com> (Tim Cross's message of "Wed, 5 Sep 2012 08:43:19 +1000")
Tim Cross <theophilusx@gmail.com> writes:
[snip]
> 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.
If you know the revision that corresponds to the emacs-24.2 tag
upstream, why don't you tag your private branch yourself?
You can create tags in your private checkouts as you please, although I
would not use a name that you know exists elsewhere, just in case.
BTW, in this case you are not interested on the merge revision that
incorporated the emacs-24 VC history intro `trunk', but on the revision
that comes from the emacs-24 branch and was tagged as `emacs-24.2'.
next prev parent reply other threads:[~2012-09-05 2:34 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
2012-09-05 1:53 ` Stephen J. Turnbull
2012-09-05 2:34 ` Óscar Fuentes [this message]
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=874nndkxj2.fsf@wanadoo.es \
--to=ofv@wanadoo.es \
--cc=emacs-devel@gnu.org \
--cc=theophilusx@gmail.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).