unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Bastien <bastienguerry@googlemail.com>
To: B Smith-Mannschott <bsmith.occs@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Switching to bzr: what Emacs developers should know?
Date: Sun, 09 Aug 2009 06:40:58 +0800	[thread overview]
Message-ID: <87vdkykjyd.fsf@bzg.ath.cx> (raw)
In-Reply-To: <28c656e20908081151h55a4b566v4cfc7c49c5ca2a37@mail.gmail.com> (B. Smith-Mannschott's message of "Sat, 8 Aug 2009 20:51:31 +0200")

B Smith-Mannschott <bsmith.occs@gmail.com> writes:

> On Sat, Aug 8, 2009 at 18:24, Bastien<bastienguerry@googlemail.com> wrote:
>> Can someone describe the bzr workflow for Emacs developers?
>
> Presumably, you've seen this, yes?:
> http://www.emacswiki.org/emacs/BzrForEmacsDevs

Now I have, thanks.  Will send some comments in another message.

> Well, the wiki page currently only says:
>
> [quote]
> Merging Upstream Packages (e.g., Gnus) Into Emacs With Bazaar
>
> TODO: TBD (but frankly, this should be easy, as it fits perfectly with
> the DVCS/Bazaar model anyway)
> [/quote]

I hope someone will do this, it was the part I was particularily
interested in.

Thanks,

-- 
 Bastien




  parent reply	other threads:[~2009-08-08 22:40 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-08 16:24 Switching to bzr: what Emacs developers should know? Bastien
2009-08-08 18:51 ` B Smith-Mannschott
2009-08-08 19:54   ` Stefan Monnier
2009-08-08 22:41     ` Bastien
2009-08-09  1:23       ` Stefan Monnier
2009-08-11  5:42         ` Karl Fogel
2009-08-11  5:49     ` Karl Fogel
2009-08-11 17:17       ` Stefan Monnier
     [not found]         ` <87fxbyb3s5.fsf@notengoamigos.org>
2009-08-13 16:21           ` Stefan Monnier
2009-08-11 18:56       ` bzr for Gnus (was: Switching to bzr: what Emacs developers should know?) Ted Zlatanov
2009-08-12  5:28         ` Stephen J. Turnbull
2009-08-12 13:50           ` Mike Kupfer
2009-08-12 15:09             ` bzr for Gnus Ted Zlatanov
2009-09-08 16:27               ` Karl Fogel
2009-09-09  3:11                 ` Stefan Monnier
2009-08-12  8:01         ` Miles Bader
2009-08-13 16:38           ` Stefan Monnier
2009-08-08 22:40   ` Bastien [this message]
2009-08-09  0:03   ` Switching to bzr: what Emacs developers should know? Bastien
2009-08-09  2:24     ` Óscar Fuentes
2009-08-18  9:31       ` Bastien
2009-08-09 12:42   ` CHENG Gao
2009-08-11  5:44     ` Karl Fogel
     [not found]       ` <8763cua0za.fsf@notengoamigos.org>
2009-08-11 15:19         ` Karl Fogel
     [not found]           ` <87ocqmb587.fsf@notengoamigos.org>
2009-08-11 18:20             ` Karl Fogel
     [not found]               ` <87bpmmb27v.fsf@notengoamigos.org>
2009-08-11 19:15                 ` Karl Fogel
2009-08-12  5:50               ` CHENG Gao
2009-08-13 16:31               ` 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

  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=87vdkykjyd.fsf@bzg.ath.cx \
    --to=bastienguerry@googlemail.com \
    --cc=bsmith.occs@gmail.com \
    --cc=emacs-devel@gnu.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).