From: Christoph <cschol2112@googlemail.com>
To: Lennart Borgman <lennart.borgman@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs 23.2.94 pretest
Date: Wed, 23 Feb 2011 17:28:29 -0700 [thread overview]
Message-ID: <86hbbup976.fsf@gmail.com> (raw)
In-Reply-To: <AANLkTi=BPpwbeMwkuCavesnOWggf+01y0PsU_vwF+zTL@mail.gmail.com> (Lennart Borgman's message of "Wed, 23 Feb 2011 21:41:59 +0100")
Lennart Borgman <lennart.borgman@gmail.com> writes:
> Is there anything that prevents naming the uploaded binaries after the
> bzr rev number/id?
Just the .zip file? Or the 24.0.50 folder contained in it?
I agree that we should identify the weekly trunk snapshot Sean builds
with a bzr revision id. However, this should be an automated process
executed when running `make dist' and not some manual (error-prone)
renaming.
Once I finish the Python cleanup I am working on right now, I want to
try to extend the `make dist' rule to incorporate this.
The sole purpose of this would be to tie the weekly Windows snapshot to
a revision in bzr for troubleshooting. Since the bzr revision is not
unique across branches it is not very useful for general Emacs builds
unless one can be sure the source of the build is the trunk.
I will think more about this, maybe there is a solution that works for
all builds on all systems.
Christoph
next prev parent reply other threads:[~2011-02-24 0:28 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-15 4:46 Emacs 23.2.94 pretest Chong Yidong
2011-02-15 4:54 ` Miles Bader
2011-02-15 15:49 ` Chong Yidong
2011-02-15 18:43 ` copyright-update in nnfolder [was Re: Emacs 23.2.94 pretest] Glenn Morris
2011-02-15 20:30 ` Stefan Monnier
2011-02-16 2:22 ` Miles Bader
2011-02-16 21:28 ` Emacs 23.2.94 pretest Lars Ingebrigtsen
2011-02-17 1:00 ` Sean Sieger
2011-02-23 17:36 ` Uday S Reddy
2011-02-23 17:44 ` Chong Yidong
2011-02-23 17:51 ` Uday S Reddy
2011-02-23 19:01 ` Chong Yidong
2011-02-23 19:27 ` Eli Zaretskii
2011-02-23 20:36 ` Uday S Reddy
2011-02-23 20:41 ` Lennart Borgman
2011-02-24 0:28 ` Christoph [this message]
2011-02-23 21:21 ` Chong Yidong
2011-02-23 21:51 ` Eli Zaretskii
2011-02-23 23:11 ` Chong Yidong
2011-02-23 23:35 ` Uday Reddy
2011-02-24 3:54 ` Eli Zaretskii
2011-02-23 23:46 ` Uday S Reddy
2011-02-23 17:59 ` Eli Zaretskii
2011-02-24 1:13 ` Sean Sieger
2011-02-24 4:01 ` Eli Zaretskii
[not found] ` <4D669A15.9080701@online.de>
2011-02-24 18:09 ` Chong Yidong
2011-02-24 18:56 ` Andreas Schwab
2011-02-24 21:26 ` Andreas Röhler
2011-02-24 22:20 ` Davis Herring
2011-02-25 6:46 ` Andreas Röhler
2011-02-25 9:32 ` Andreas Schwab
2011-02-25 10:09 ` Andreas Röhler
2011-02-25 7:01 ` Andreas Röhler
2011-02-25 13:35 ` Davis Herring
2011-02-25 10:18 ` Andreas Röhler
2011-02-25 10:29 ` Andreas Schwab
2011-02-25 11:31 ` Andreas Röhler
2011-02-25 11:43 ` Andreas Röhler
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=86hbbup976.fsf@gmail.com \
--to=cschol2112@googlemail.com \
--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).