From: Junio C Hamano <gitster@pobox.com>
To: "Sverre Hvammen Johansen" <hvammen@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Merging using only fast-forward
Date: Sat, 19 Jan 2008 02:43:57 -0800 [thread overview]
Message-ID: <7vzlv2858y.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <402c10cd0801190228o68995493u9b8b40e1557092dd@mail.gmail.com> (Sverre Hvammen Johansen's message of "Sat, 19 Jan 2008 02:28:55 -0800")
"Sverre Hvammen Johansen" <hvammen@gmail.com> writes:
> The more I think about this is that --ff-only should really be
> specified as a merge strategy (single) and not as an special case of
> --ff. All merge strategies can then take any number of commits, but
> will only succeed if the commits can be reduced down to two or fewer
> for resolve/recursive and one for single.
Interesting.
At one end of the spectrum, we have these crazy people who want
git to record something that is not a merge at all as a merge
with --no-ff. At the other end of the spectrum, we have these
other crazy people who want git to outsmart them by allowing
them to throw random set of commits as potential parents,
remove duplicates and figure out how many real parents the
resulting merge should have (including the case that it may not
even have any).
I'll have to think about it, but it sounds like a promising
idea.
next prev parent reply other threads:[~2008-01-19 10:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-16 15:54 Merging using only fast-forward Sverre Hvammen Johansen
2008-01-16 16:27 ` Randal L. Schwartz
2008-01-16 20:31 ` Junio C Hamano
2008-01-16 22:38 ` Sverre Hvammen Johansen
2008-01-16 22:49 ` Junio C Hamano
2008-01-17 6:53 ` Sverre Hvammen Johansen
2008-01-18 6:58 ` Sverre Hvammen Johansen
2008-01-18 21:25 ` Junio C Hamano
2008-01-19 10:28 ` Sverre Hvammen Johansen
2008-01-19 10:38 ` Sverre Hvammen Johansen
2008-01-19 10:43 ` Junio C Hamano [this message]
[not found] ` <402c10cd0801190427o62493073s408959aa5701ca86@mail.gmail.com>
2008-01-19 12:30 ` Sverre Hvammen Johansen
2008-01-19 12:58 ` Please don't reply to this thread Sverre Hvammen Johansen
2008-01-19 12:39 ` Merging using only fast-forward Sverre Hvammen Johansen
2008-01-21 6:26 ` Sverre Hvammen Johansen
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=7vzlv2858y.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=hvammen@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).