From: Eli Zaretskii <eliz@gnu.org>
To: Lennart Borgman <lennart.borgman@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Next pretest, and branching plans
Date: Sun, 21 Feb 2010 06:11:27 +0200 [thread overview]
Message-ID: <83eikfw7m8.fsf@gnu.org> (raw)
In-Reply-To: <e01d8a51002201611k1c0116e6r8556d88b501cce6f@mail.gmail.com>
> From: Lennart Borgman <lennart.borgman@gmail.com>
> Date: Sun, 21 Feb 2010 01:11:22 +0100
> Cc: Drew Adams <drew.adams@oracle.com>, emacs-devel@gnu.org
>
> I just uploaded new unpatched binaries as I told. However I wonder if
> I was uploading the right thing from a pretest point of view.
>
> If I already have Emacs sources checked out (which I have of course)
> is there a way to build pretest binaries from what I have? I have no
> idea about how the branches and bazaar works for this.
The easiest way is to build the pretest sources downloaded from
alpha.gnu.org.
It is also possible to find out the revision number of the tree from
which the pretest tarball was tarred, then "bzr revert" to that
revert, and build it. But I don't see how this is easier.
next prev parent reply other threads:[~2010-02-21 4:11 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-18 11:02 Next pretest, and branching plans Chong Yidong
2010-02-18 15:29 ` Drew Adams
2010-02-20 12:25 ` Leo
2010-02-20 13:05 ` Sean Sieger
2010-02-20 17:02 ` Drew Adams
2010-02-28 12:36 ` Sean Sieger
2010-02-28 15:13 ` Lennart Borgman
2010-02-20 16:52 ` Drew Adams
2010-02-20 17:35 ` Drew Adams
2010-02-20 19:45 ` Eli Zaretskii
2010-02-20 20:39 ` Drew Adams
2010-02-20 20:53 ` Lennart Borgman
2010-02-21 0:11 ` Lennart Borgman
2010-02-21 4:11 ` Eli Zaretskii [this message]
2010-02-20 17:51 ` Eli Zaretskii
2010-02-20 18:35 ` Drew Adams
2010-02-20 19:49 ` Eli Zaretskii
2010-02-20 18:36 ` Chong Yidong
2010-02-20 18:40 ` Drew Adams
2010-02-20 18:54 ` Lennart Borgman
2010-02-20 19:15 ` Drew Adams
2010-02-20 19:08 ` Lennart Borgman
2010-02-18 23:57 ` Emacs Manuals Richard Stallman
2010-02-20 2:46 ` smc
[not found] <4B8147A9.7030504@gmail.com>
[not found] ` <87ljemdzxo.fsf@stupidchicken.com>
2010-02-23 5:31 ` Next pretest, and branching plans Jason Rumney
2010-02-23 18:29 ` Eli Zaretskii
2010-02-23 21:12 ` Jason Rumney
2010-02-24 6:04 ` Richard Stallman
2010-02-24 13:34 ` Sean Sieger
2010-02-24 15:05 ` Davis Herring
2010-02-24 15:18 ` Sean Sieger
2010-02-24 14:05 ` Chong Yidong
2010-02-25 14:26 ` Richard Stallman
2010-02-27 16:52 ` Johan Bockgård
2010-03-03 3:52 ` Glenn Morris
2010-03-05 0:31 ` Johan Bockgård
2010-03-13 3:10 ` Christoph
2010-03-13 7:42 ` Eli Zaretskii
2010-03-13 14:54 ` Christoph
2010-03-13 18:30 ` Stefan Monnier
2010-03-13 19:06 ` Eli Zaretskii
2010-03-14 2:38 ` Jason Rumney
2010-03-14 2:50 ` Christoph
2010-03-14 3:07 ` Jason Rumney
2010-03-14 17:55 ` Eli Zaretskii
2010-03-17 0:29 ` Christoph
2010-03-17 4:14 ` Eli Zaretskii
2010-03-17 12:44 ` Jason Rumney
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=83eikfw7m8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=lennart.borgman@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).