From: "Óscar Fuentes" <ofv@wanadoo.es>
To: emacs-devel@gnu.org
Subject: Re: bzr workflow
Date: Wed, 13 Jan 2010 09:31:05 +0100 [thread overview]
Message-ID: <87fx6a1k52.fsf@telefonica.net> (raw)
In-Reply-To: 87r5puspr5.fsf@red-bean.com
Karl Fogel <kfogel@red-bean.com> writes:
> 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? :-)
Personally, I prefer the conceptual simplicity of using trunk/ as the
gateway to upstream and do not overload it with other uses. It costs
nothing to bind quickfixes/ to upstream as trunk/ already is. I think
that if people use trunk/ for hacking, eventually it will get polluted
by half done quickfixes and will inhibit the use of feature branches
(because you need to clean up trunk/ before merging the feature branch
into upstream, etc), thus involuntarily encouraging a disorganized
personal development model, as was the case with CVS.
--
Óscar
next prev parent reply other threads:[~2010-01-13 8:31 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
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 [this message]
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
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=87fx6a1k52.fsf@telefonica.net \
--to=ofv@wanadoo.es \
--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).