From: Kenichi Handa <handa@m17n.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: New branch
Date: Wed, 03 Feb 2010 10:05:03 +0900 [thread overview]
Message-ID: <tl7636fuo1s.fsf@m17n.org> (raw)
In-Reply-To: <jwvtyu7gdva.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Wed, 27 Jan 2010 21:37:34 -0500)
In article <jwvtyu7gdva.fsf-monnier+emacs@gnu.org>, Stefan Monnier <monnier@iro.umontreal.ca> writes:
> I have just opened a new branch sftp://bzr.sv.gnu.org/srv/bzr/emacs/pending
> which is intended to receive patches that cannot be installed in trunk
> because they're not bug-fixes.
> I.e. the branch is there so instead of saying "please come back later"
> we can just install the corresponding patch/package into this branch.
Please teach me the bzr command sequence to do that. Should
I repeast this same procedure used for checking out trunk
branch?
% cd emacs
% bzr branch sftp://USERNAME@bzr.savannah.gnu.org/srv/bzr/emacs/trunk trunk
% cd trunk
% echo "public_branch = sftp://USERNAME@bzr.savannah.gnu.org/srv/bzr/emacs/trunk" >> .bzr/branch/branch.conf
% bzr bind sftp://USERNAME@bzr.savannah.gnu.org/srv/bzr/emacs/trunk
% cd ..
Or, can I use some shortcut to utilize the
already-checked-out trunk branch?
---
Kenichi Handa
handa@m17n.org
next prev parent reply other threads:[~2010-02-03 1:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-28 2:37 New branch Stefan Monnier
2010-01-28 5:40 ` Eli Zaretskii
2010-01-28 19:13 ` Stefan Monnier
2010-01-28 19:41 ` Óscar Fuentes
2010-01-28 20:12 ` Chong Yidong
2010-01-28 21:08 ` Eli Zaretskii
2010-01-28 22:53 ` Stefan Monnier
2010-01-28 23:22 ` Óscar Fuentes
2010-01-29 1:55 ` Stefan Monnier
2010-01-29 4:24 ` Stephen J. Turnbull
2010-01-29 5:13 ` Stefan Monnier
2010-02-03 1:05 ` Kenichi Handa [this message]
2010-02-03 2:31 ` Stefan Monnier
2010-02-03 4:24 ` Kenichi Handa
2010-02-03 14:20 ` Stefan Monnier
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=tl7636fuo1s.fsf@m17n.org \
--to=handa@m17n.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.