From: Christoph <cschol2112@googlemail.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: emacs-devel@gnu.org
Subject: Re: Review: make-tarball.txt
Date: Mon, 01 Mar 2010 21:26:05 -0700 [thread overview]
Message-ID: <4B8C935D.9000200@gmail.com> (raw)
In-Reply-To: <m3eik9wtxo.fsf@hase.home>
On 2/25/2010 2:22 AM, Andreas Schwab wrote:
> Christoph<cschol2112@googlemail.com> writes:
>
>> + bzr tag EMACS_`NUMBER'_BASE
>>
> There is no need for the base tag any more.
>
>
>> + bzr branch -r tag:EMACS_`NUMBER'_BASE ./ ../EMACS_`NUMBER'_RC
>>
> The branch should get a less shouting name, like emacs-$NUMBER. (The RC
> suffix has always been a stupid convention.)
>
> Andreas
Andreas,
What would you propose?
Just
bzr branch ./ ../emacs-$NUMBER
to cut the branch for release?
Christoph
prev parent reply other threads:[~2010-03-02 4:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-25 3:32 Review: make-tarball.txt Christoph
2010-02-25 9:22 ` Andreas Schwab
2010-03-02 4:26 ` Christoph [this message]
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=4B8C935D.9000200@gmail.com \
--to=cschol2112@googlemail.com \
--cc=emacs-devel@gnu.org \
--cc=schwab@linux-m68k.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).