From: "Óscar Fuentes" <ofv@wanadoo.es>
To: "Stephen J. Turnbull" <stephen@xemacs.org>
Cc: Tim Cross <theophilusx@gmail.com>, emacs-devel@gnu.org
Subject: Re: Release tags
Date: Wed, 05 Sep 2012 05:49:24 +0200 [thread overview]
Message-ID: <87zk55jfi3.fsf@wanadoo.es> (raw)
In-Reply-To: <87392xtbei.fsf@uwakimon.sk.tsukuba.ac.jp> (Stephen J. Turnbull's message of "Wed, 05 Sep 2012 12:07:49 +0900")
"Stephen J. Turnbull" <stephen@xemacs.org> writes:
> Óscar Fuentes writes:
>
> > If you know the revision that corresponds to the emacs-24.2 tag
> > upstream, why don't you tag your private branch yourself?
>
> Because he doesn't have that revision to tag. If he did, he'd have
> the tag, too.
No, he says that he has an up-to-date checkout of `trunk', which
necessarily contains the revision tagged as `emacs-24.2', because it was
merged into `trunk' almost 2 weeks ago. He also mentions that he knows
the revision number of the merge. His problem is that the tag (not the
revision) is missing from his private repo.
> So he would need to branch emacs-24.2, and he doesn't
> want to do that (I'm not sure why, so I asked, we'll see what he
> says).
Dealing with multiple branches on bzr is a bit of an inconvenience, for
several reasons. One of them is mentioned by the OP: you end having
multiple working copies around, or having to learn and remember tricks
for reusing the same working copy. As the OP plans to use the emacs-24.2
stable point only in the rare cases when `trunk' is in a unusable state,
his reluctance is understandable.
next prev parent reply other threads:[~2012-09-05 3:49 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
2012-09-05 3:07 ` Stephen J. Turnbull
2012-09-05 3:49 ` Óscar Fuentes [this message]
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=87zk55jfi3.fsf@wanadoo.es \
--to=ofv@wanadoo.es \
--cc=emacs-devel@gnu.org \
--cc=stephen@xemacs.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).