From: Sam Steingold <sds@gnu.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: emacs-devel@gnu.org
Subject: Re: bzr workflow
Date: Mon, 11 Jan 2010 16:57:25 -0500 [thread overview]
Message-ID: <1f77704b1001111357l29886b88oaf1da0ddbb12db62@mail.gmail.com> (raw)
In-Reply-To: <m2aawkxr2w.fsf@igel.home>
On 1/11/10, Andreas Schwab <schwab@linux-m68k.org> wrote:
> Sam Steingold <sds@gnu.org> writes:
>
> > 1. Am I the only one who thinks this is a little too convoluted? (the only
> > other DVC I regularly use is hg, and there the workflow is "commit+push"
> > instead of the recommended emacs workflow "commit+merge+commit").
>
>
> Nothing stops you from using the more advanced workflow.
what "more advanced workflow"?
http://www.emacswiki.org/emacs/BzrForEmacsDevs
It might occur to you to save some effort by just doing bzr push
directly to the upstream master from inside the quickfixes branch:
cd $DEVHOME/emacs/quickfixes
bzr push sftp://USERNAME@bzr.savannah.gnu.org/srv/bzr/emacs/trunk/
Do not do this — it can cause history to be displayed in a strange way
in the upstream master, any mirrors or branches of it, and your own
branch later. Search for the word “hidden” in this mail for more
details.
--
Sam Steingold <http://sds.podval.org>
next prev parent reply other threads:[~2010-01-11 21:57 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 [this message]
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
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=1f77704b1001111357l29886b88oaf1da0ddbb12db62@mail.gmail.com \
--to=sds@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=schwab@linux-m68k.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).