unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Bill Wohler <wohler@newt.com>
To: emacs-devel@gnu.org
Subject: Re: Bzr Emacs question
Date: Sat, 24 Nov 2012 10:22:28 -0800	[thread overview]
Message-ID: <87mwy6uahn.fsf@olgas.newt.com> (raw)
In-Reply-To: 83mwy6zx7z.fsf@gnu.org

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.

>> Note that "bzr help revisionspec" says:
>> 
>>     Alternately, [the revision] can be given without a keyword, in which
>>     case it will be checked as a revision number, a tag, a revision id,
>>     a date specification, or a branch specification, in that order.
>
> And you are willing to bet your life on that it guesses right? ;-)

Ha! No, but I'd bet a beer :-).

>> > (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.

Thanks very much for your help.

-- 
Bill Wohler <wohler@newt.com> aka <Bill.Wohler@nasa.gov>
http://www.newt.com/wohler/
GnuPG ID:610BD9AD




  reply	other threads:[~2012-11-24 18:22 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 [this message]
2012-11-24 20:43         ` Eli Zaretskii
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

  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=87mwy6uahn.fsf@olgas.newt.com \
    --to=wohler@newt.com \
    --cc=emacs-devel@gnu.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).