From: Junio C Hamano <gitster@pobox.com>
To: Martin von Zweigbergk <martinvonz@gmail.com>
Cc: Christian Couder <christian.couder@gmail.com>,
"Patricia B. C." <pati.camsky@gmail.com>,
git <git@vger.kernel.org>
Subject: Re: Can git change?
Date: Fri, 22 Jan 2021 18:27:30 -0800 [thread overview]
Message-ID: <xmqqh7n85qwd.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <CANiSa6gEJ8ezVLhHf+TkGpqvEwvb8HhqtU3ETKiopjLQj6E_QQ@mail.gmail.com> (Martin von Zweigbergk's message of "Fri, 22 Jan 2021 12:43:53 -1000")
Martin von Zweigbergk <martinvonz@gmail.com> writes:
> This is probably quite off topic for the thread, but I'm curious why
> you think it was a bad idea to have octopus merges in git.git's
> history (there seem to be 37 of them).
Octoupi in our history, at least the older ones, solve no real life
problem; it only gives us "now we have something cool-looking that
other people's version control systems never had", which is of
dubious value.
And their presense makes bisection less efficient than it could be
around them, which is a real downside.
next prev parent reply other threads:[~2021-01-23 2:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-22 12:59 Can git change? Patricia B. C.
2021-01-22 13:31 ` Christian Couder
2021-01-22 18:46 ` Junio C Hamano
2021-01-22 22:43 ` Martin von Zweigbergk
2021-01-23 2:27 ` Junio C Hamano [this message]
2021-01-23 12:56 ` RES: " Patricia B. C.
2021-01-25 16:28 ` Johannes Schindelin
2021-01-26 1:58 ` Junio C Hamano
2021-01-26 12:32 ` Patricia B. C.
2021-03-09 14:54 ` Daniel Gruesso
[not found] ` <CAFdpPnBG==5L6hwH6h2JTFtYVQqLZUcCi4+wzL_cpKKg_X3yoA@mail.gmail.com>
2021-03-10 21:03 ` Johannes Schindelin
2021-03-10 21:39 ` Junio C Hamano
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=xmqqh7n85qwd.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=martinvonz@gmail.com \
--cc=pati.camsky@gmail.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).