all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Karl Fogel <kfogel@red-bean.com>
To: "Stephen J. Turnbull" <stephen@xemacs.org>
Cc: "Óscar Fuentes" <ofv@wanadoo.es>,
	"Juanma Barranquero" <lekktu@gmail.com>,
	"Jan Djärv" <jan.h.d@swipnet.se>,
	emacs-devel@gnu.org
Subject: Re: bzr workflow
Date: Tue, 12 Jan 2010 21:27:42 -0500	[thread overview]
Message-ID: <87r5puspr5.fsf@red-bean.com> (raw)
In-Reply-To: <87fx6a3fyn.fsf@uwakimon.sk.tsukuba.ac.jp> (Stephen J. Turnbull's message of "Wed, 13 Jan 2010 11:18:24 +0900")

"Stephen J. Turnbull" <stephen@xemacs.org> writes:
>FWIW, the real reason that we didn't say anything about it is that the
>original idea was that the trunk would be treeless, but it turns out
>that you can't merge a branch without a tree.  (It's not impossible in
>theory -- eg, if the divergent changes affect different files -- but
>bzr won't do it.)

I think it was that, and a desire not to throw too many different ways
of doing things at newbies.

But at this point, I think we could update the BzrForEmacsDevs doc to
recommend just doing trivial mods in trunk and committing directly from
there.  Heck, that's what I'm doing with really simple stuff.

Can anyone think of any gotchas?  Particularly gotchas that would lead
to people on this list having to provide more support not less? :-)




  parent reply	other threads:[~2010-01-13  2:27 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-11 21:10 bzr workflow Sam Steingold
2010-01-11 21:35 ` Andreas Schwab
2010-01-11 21:57   ` Sam Steingold
2010-01-11 23:05     ` Andreas Schwab
2010-01-11 21:37 ` Óscar Fuentes
2010-01-11 22:13   ` Chong Yidong
2010-01-12  7:47   ` Jan Djärv
2010-01-12  8:40     ` Óscar Fuentes
2010-01-12  9:39       ` Jan Djärv
2010-01-12  9:48         ` Óscar Fuentes
2010-01-12 19:41         ` Eli Zaretskii
2010-01-13  7:24           ` Jan D.
2010-01-13  0:01         ` Juanma Barranquero
2010-01-13  2:18           ` Stephen J. Turnbull
2010-01-13  2:16             ` Juanma Barranquero
2010-01-13  3:23               ` Stephen J. Turnbull
2010-01-13  3:29                 ` Lennart Borgman
2010-01-13  4:18                   ` Eli Zaretskii
2010-01-13  4:56                     ` Lennart Borgman
2010-01-13  8:48                       ` Stephen J. Turnbull
2010-01-13  3:53                 ` Juanma Barranquero
2010-01-13  2:27             ` Karl Fogel [this message]
2010-01-13  4:02               ` Stephen J. Turnbull
2010-01-13  4:20                 ` Eli Zaretskii
2010-01-13 16:55                 ` Karl Fogel
2010-01-13  4:17               ` Eli Zaretskii
2010-01-13  8:31               ` Óscar Fuentes
2010-01-12 19:35     ` Eli Zaretskii
2010-01-11 22:08 ` Eli Zaretskii

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=87r5puspr5.fsf@red-bean.com \
    --to=kfogel@red-bean.com \
    --cc=emacs-devel@gnu.org \
    --cc=jan.h.d@swipnet.se \
    --cc=lekktu@gmail.com \
    --cc=ofv@wanadoo.es \
    --cc=stephen@xemacs.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 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.