From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Ken Raeburn <raeburn@raeburn.org>
Cc: Emacs development discussions <emacs-devel@gnu.org>
Subject: Re: emacs bzr and git-bzr
Date: Tue, 05 Jan 2010 10:26:48 -0500 [thread overview]
Message-ID: <jwv4on0o9nc.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <B130A3A3-0079-41EC-AEBF-0E0FE49DBB93@raeburn.org> (Ken Raeburn's message of "Tue, 5 Jan 2010 08:44:28 -0500")
> Is there a way to use one of the "git-bzr" scripts out there that's safe and
> consistent with the way we want to use bzr for emacs development?
I'd ask on a git-bzr list rather than here,
Stefan
next prev parent reply other threads:[~2010-01-05 15:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-05 13:44 emacs bzr and git-bzr Ken Raeburn
2010-01-05 15:26 ` Stefan Monnier [this message]
2010-01-05 17:07 ` Jonas Bernoulli
2010-01-06 15:19 ` Ken Raeburn
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=jwv4on0o9nc.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=raeburn@raeburn.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).