unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: joakim@verona.se, emacs-devel@gnu.org
Subject: Re: adding branches to bzr?
Date: Wed, 13 Jan 2010 23:29:06 -0500	[thread overview]
Message-ID: <jwv4omptirg.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87y6k1k7zd.fsf@stupidchicken.com> (Chong Yidong's message of "Wed, 13 Jan 2010 16:31:02 -0500")

> I haven't had time to properly think about this yet.
> My understanding is that there's negligible cost to adding multiple bzr
> branches to the central repo (in terms of, say, server resources or bzr
> log output).  Is that right?  If so, I guess it won't hurt to start
> making branches for the features lined up for Emacs 24 (which we'll
> begin concentrating on in a couple months, once 23.2 draws closer to
> release).

I'd tend to agree.  We could create a subdirectory for working branches
where people could install their work in progress when they need to
share them.  Admittedly, if I had such a branch, I'd put it elsewhere to
avoid the sftp overhead.

But Stephen's point is also relevant: we want those branches to be
"clean" in the sense that they should be based on the current Bzr
repository, so branches that started elsewhere would need to be rebased
before installing them.


        Stefan




      parent reply	other threads:[~2010-01-14  4:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-13  7:39 adding branches to bzr? joakim
2010-01-13  8:43 ` Óscar Fuentes
2010-01-13  8:55 ` Stephen J. Turnbull
2010-01-13 12:17 ` Richard Stallman
2010-01-13 13:13   ` joakim
2010-01-13 21:31 ` Chong Yidong
2010-01-13 22:44   ` Karl Fogel
2010-01-14  1:21     ` Stephen J. Turnbull
2010-01-14  4:29   ` Stefan Monnier [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=jwv4omptirg.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=cyd@stupidchicken.com \
    --cc=emacs-devel@gnu.org \
    --cc=joakim@verona.se \
    /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).