From: Junio C Hamano <gitster@pobox.com>
To: "Sverre Hvammen Johansen" <hvammen@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [RFC/PATCH] Fast forward strategies only, common, fork and path
Date: Mon, 04 Feb 2008 00:22:20 -0800 [thread overview]
Message-ID: <7v8x21ku6b.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <402c10cd0802040006yb654688l8dfc7140c507bc26@mail.gmail.com> (Sverre Hvammen Johansen's message of "Mon, 4 Feb 2008 00:06:09 -0800")
"Sverre Hvammen Johansen" <hvammen@gmail.com> writes:
> ... However, it might take some time. What is the
> time-frame for inclusion in 1.5.5?
The 1.5.4 cycle was too long (5 months). A regular interval
ought to be about 3 months but I'd really like to keep 1.5.5
focused on obvious and unanimously supported changes that do not
impact the existing semantics deeply, and keep it shorter than
that.
I think it is too early to tell if this topic falls into that
category. The patch is only a few day old, and there has been
no real discussion nor comments on it yet. I also felt that the
backstory was lacking and it would be hard to judge for people
other than yourself how useful the new ff substrategies are in
what context.
The documentation updates talked about what the options do, but
it was unclear why they could be useful in what situations and
workflows. At least it was not apparent to me on my cursory
read.
> --ff=never will turn this off together with fast forward. Maybe we
> should have --ff=traditional that is the old behavior.
Sure, and I mildly suspect that it should be the default.
next prev parent reply other threads:[~2008-02-04 8:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-04 0:54 [RFC/PATCH] Fast forward strategies only, common, fork and path Sverre Hvammen Johansen
2008-02-04 4:49 ` Stefan (metze) Metzmacher
2008-02-04 6:51 ` Sverre Hvammen Johansen
2008-02-04 7:24 ` Junio C Hamano
2008-02-04 8:06 ` Sverre Hvammen Johansen
2008-02-04 8:22 ` Junio C Hamano [this message]
2008-02-05 7:32 ` Sverre Hvammen Johansen
2008-02-05 9:34 ` Jakub Narebski
2008-02-05 9:40 ` Junio C Hamano
2008-02-06 3:46 ` Sverre Hvammen Johansen
2008-02-04 7:13 ` Sverre Hvammen Johansen
2008-02-04 7:31 ` Junio C Hamano
2008-02-04 7:43 ` Sverre Hvammen Johansen
2008-02-04 7:19 ` 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=7v8x21ku6b.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).