From: Barry Warsaw <barry@python.org>
To: emacs-devel@gnu.org
Subject: Re: Messing with the VC history
Date: Tue, 18 Nov 2014 11:47:47 -0500 [thread overview]
Message-ID: <20141118114747.242a35c7@anarchist.wooz.org> (raw)
In-Reply-To: 878uj9uepz.fsf@uwakimon.sk.tsukuba.ac.jp
[-- Attachment #1: Type: text/plain, Size: 666 bytes --]
On Nov 18, 2014, at 04:53 PM, Stephen J. Turnbull wrote:
>I find bisect very useful on occasion, so would rule out Type A if at all
>possible. But I find Type B plausible, and think it's a matter of taste.
bisect would be more useful, IMHO, if it followed first-parents by default.
IOW, when merging a feature branch into "mainline", I don't care whether
intermediate commits on the feature branch don't pass all their tests. I *do*
care that every commit on "mainline" passes all their tests.
>[1] However, some people think a mainline with only merge commits on
>it is pretty, and they just oppose rebasing on principle.
\o
Cheers,
-Barry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-11-18 16:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-16 6:17 Messing with the VC history Óscar Fuentes
2014-11-16 8:19 ` Achim Gratz
2014-11-16 15:25 ` Eli Zaretskii
2014-11-16 16:00 ` David Engster
2014-11-17 16:48 ` Eli Zaretskii
2014-11-16 16:33 ` Achim Gratz
2014-11-16 18:13 ` Eli Zaretskii
2014-11-22 10:04 ` Steinar Bang
2014-11-16 15:24 ` Eli Zaretskii
2014-11-16 16:05 ` Óscar Fuentes
2014-11-16 16:21 ` Eli Zaretskii
2014-11-16 23:33 ` Stephen J. Turnbull
2014-11-17 1:31 ` John Yates
2014-11-17 3:23 ` Stephen J. Turnbull
2014-11-18 7:18 ` Lars Brinkhoff
2014-11-18 7:42 ` David Kastrup
2014-11-18 7:53 ` Stephen J. Turnbull
2014-11-18 8:41 ` David Kastrup
2014-11-18 16:47 ` Barry Warsaw [this message]
2014-11-18 17:06 ` Andreas Schwab
2014-11-18 22:30 ` Stephen J. Turnbull
2014-11-19 2:34 ` Stefan Monnier
2014-11-17 16:42 ` 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=20141118114747.242a35c7@anarchist.wooz.org \
--to=barry@python.org \
--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).