From: Eli Zaretskii <eliz@gnu.org>
To: "Stephen J. Turnbull" <stephen@xemacs.org>
Cc: tzz@lifelogs.com, ding@gnus.org, emacs-devel@gnu.org
Subject: Re: Gnus overrides.texi and WEBHACKDEVEL
Date: Sun, 06 Feb 2011 20:50:46 +0200 [thread overview]
Message-ID: <838vxtt2t5.fsf@gnu.org> (raw)
In-Reply-To: <874o8h124y.fsf@uwakimon.sk.tsukuba.ac.jp>
> From: "Stephen J. Turnbull" <stephen@xemacs.org>
> Cc: tzz@lifelogs.com,
> ding@gnus.org,
> emacs-devel@gnu.org
> Date: Mon, 07 Feb 2011 02:52:45 +0900
>
> But it's a simple, generic observation: if you have some changes that
> should be pushed, and others (that may be worth preserving) that
> should not be pushed, use a branch to work in. Then cherrypick the
> changes to your integration workspace (which can be a branch or a
> checkout). Finally push the commits from the integration workspace.
If this is what you had in mind, then it's still manual work, and
thus prone to errors. I can do the same in a bound branch with
"bzr ci FILE1 FILE2 ...", thus "cherrypicking" only what should be
pushed.
The original problem was that some people do not pay attention to what
"bzr status" says, and just do a "bzr ci", which pushes all the
modified files. I guess there's no way around vigilance. Which is
fine with me.
Thanks.
next prev parent reply other threads:[~2011-02-06 18:50 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-05 9:35 Revision 103117 on the Emacs trunk Eli Zaretskii
2011-02-05 9:52 ` Katsumi Yamaoka
2011-02-05 11:47 ` Eli Zaretskii
2011-02-05 12:16 ` Katsumi Yamaoka
2011-02-07 18:29 ` Ted Zlatanov
2011-02-08 3:49 ` Eli Zaretskii
2011-02-08 8:00 ` Peter Münster
2011-02-08 8:28 ` Eli Zaretskii
2011-02-08 8:50 ` Andreas Schwab
2011-02-08 9:06 ` Peter Münster
2011-02-08 9:28 ` Eli Zaretskii
2011-02-08 14:33 ` -DWEBHACKDEVEL for Gnus (was: Revision 103117 on the Emacs trunk.) Ted Zlatanov
2011-02-08 15:23 ` -DWEBHACKDEVEL for Gnus Peter Münster
2011-02-05 13:08 ` Revision 103117 on the Emacs trunk Andreas Schwab
2011-02-05 14:21 ` Gnus overrides.texi and WEBHACKDEVEL (was: Revision 103117 on the Emacs trunk.) Ted Zlatanov
2011-02-05 15:12 ` Gnus overrides.texi and WEBHACKDEVEL Eli Zaretskii
2011-02-05 15:18 ` Ted Zlatanov
2011-02-05 15:39 ` Eli Zaretskii
2011-02-05 16:01 ` Ted Zlatanov
2011-02-07 19:06 ` Eli Zaretskii
2011-02-07 19:19 ` Ted Zlatanov
2011-02-07 19:47 ` Eli Zaretskii
2011-02-06 6:49 ` Stephen J. Turnbull
2011-02-06 10:25 ` Eli Zaretskii
2011-02-06 14:40 ` Stephen J. Turnbull
2011-02-06 17:22 ` Eli Zaretskii
2011-02-06 17:52 ` Stephen J. Turnbull
2011-02-06 18:50 ` Eli Zaretskii [this message]
2011-02-06 19:20 ` Stephen J. Turnbull
2011-02-06 21:21 ` 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=838vxtt2t5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=stephen@xemacs.org \
--cc=tzz@lifelogs.com \
/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.
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 NNTP newsgroup(s).