From: Eli Zaretskii <eliz@gnu.org>
To: Bill Wohler <wohler@newt.com>
Cc: emacs-devel@gnu.org
Subject: Re: Bzr Emacs question
Date: Sat, 24 Nov 2012 22:43:51 +0200 [thread overview]
Message-ID: <83haoezq7s.fsf@gnu.org> (raw)
In-Reply-To: <87mwy6uahn.fsf@olgas.newt.com>
> From: Bill Wohler <wohler@newt.com>
> Date: Sat, 24 Nov 2012 10:22:28 -0800
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> From: Bill Wohler <wohler@newt.com>
> >> Date: Sat, 24 Nov 2012 09:47:31 -0800
> >>
> >> > A tag is not a revision-id by itself. Try
> >> >
> >> > bzr up -r tag:mh-e-8.3.1
> >>
> >> Not surprisingly, that produces the same error.
> >
> > I guess I don't understand what your "bzr tag" command did. What is
> > "emacs-24.1" in that command?
>
> I want the mh-e-8.3.1 tag to correspond to the Emacs 24.1 release. I had
> assumed, perhaps incorrectly, that the emacs-24.1 tag was what I wanted.
In what branch did you issue that "bzr tag" command?
> >> > (And I'm not sure you really want "up" and not some other command, but
> >> > that's another story.)
> >>
> >> What would you recommend as an alternative to "svn up -r<revision>"?
> >
> > I don't know, I never used SVN seriously. What did you want to
> > accomplish?
>
> I want to grab the MH-E files associated with the Emacs 24.1 release in
> order to make an MH-E 8.3.1 release.
If you want to update the tree to a certain revision, I think
"bzr revert" is a better choice, because "update" will leave any
uncommitted changes you might have.
next prev parent reply other threads:[~2012-11-24 20:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-24 17:02 Bzr Emacs question Bill Wohler
2012-11-24 17:34 ` Eli Zaretskii
2012-11-24 17:47 ` Bill Wohler
2012-11-24 18:12 ` Eli Zaretskii
2012-11-24 18:22 ` Bill Wohler
2012-11-24 20:43 ` Eli Zaretskii [this message]
2012-11-24 20:49 ` Bill Wohler
2012-11-24 18:47 ` Bill Wohler
2012-11-24 19:50 ` Bill Wohler
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=83haoezq7s.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=wohler@newt.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 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.