From: "Sverre Hvammen Johansen" <hvammen@gmail.com>
To: "Junio C Hamano" <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 0/5] Fast forward strategies allow, never, and only
Date: Wed, 23 Apr 2008 22:39:48 -0700 [thread overview]
Message-ID: <402c10cd0804232239p3e49a6d0vdc1ff9acb3636a17@mail.gmail.com> (raw)
In-Reply-To: <7vhcdu2uu5.fsf@gitster.siamese.dyndns.org>
On Tue, Apr 22, 2008 at 12:48 AM, Junio C Hamano <gitster@pobox.com> wrote:
> Sorry, but I am with a rather big backlog and am reluctant to go back the
> archive a looong way to pick up and comment on a series when not many
> people are wondering what happened to the wonderful series ;-) Care to
> resend and ask for comments from people?
I resending these patches for you to coment. The patch series
consists of the following five patches:
0001-New-merge-tests.patch
0002-Introduce-ff-fast-forward-option.patch
0003-Restructure-git-merge.sh.patch
0004-Head-reduction-before-selecting-merge-strategy.patch
0005-Introduce-fast-forward-option-only.patch
The first patch add some tests. The second, fourth, and fifth adds
new features and they are all trivial. I was able to make the fourth
patch trivial as well by actually doing the real work of finding the
reduced parents in the third patch. The third patch computes the
reduced parents but uses it only to determine whether we are
up-to-date or do a fast forward.
There are probably some minor adjustments to the documentation we
should do. The patch series uses the term actual-parents and
reduced-parents in the code and the documentation. Maybe we should
use the term actual-heads and reduced-heads instead? I am not sure
that all the documentation for 0004 should be included. Please give
me some advise regarding this.
--
Sverre Hvammen Johansen
prev parent reply other threads:[~2008-04-24 5:40 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-11 2:59 [RFC/PATCH] Fast forward strategies allow, never, and only Sverre Hvammen Johansen
2008-03-11 3:18 ` Sverre Hvammen Johansen
2008-03-11 5:17 ` Ping Yin
2008-03-11 6:19 ` Junio C Hamano
2008-03-12 5:46 ` Sverre Hvammen Johansen
2008-03-16 6:44 ` Sverre Hvammen Johansen
2008-03-14 2:35 ` Sverre Hvammen Johansen
2008-03-11 9:15 ` Jakub Narebski
2008-03-12 4:24 ` Sverre Hvammen Johansen
2008-03-12 4:50 ` Junio C Hamano
2008-03-12 5:51 ` Sverre Hvammen Johansen
2008-03-18 4:27 ` [RFC/PATCH Second draft] " Sverre Hvammen Johansen
2008-03-18 13:57 ` Ping Yin
2008-03-18 15:58 ` Sverre Hvammen Johansen
2008-03-18 14:12 ` Jon Loeliger
2008-03-18 16:27 ` Jakub Narebski
2008-03-19 6:20 ` Sverre Hvammen Johansen
2008-03-19 21:20 ` Jakub Narebski
2008-03-20 4:44 ` Sverre Hvammen Johansen
2008-03-19 20:35 ` Junio C Hamano
2008-03-20 6:47 ` Sverre Hvammen Johansen
2008-03-22 19:49 ` Junio C Hamano
2008-03-26 3:50 ` Sverre Hvammen Johansen
2008-03-31 4:19 ` Sverre Hvammen Johansen
2008-04-20 1:06 ` [PATCH] " Sverre Hvammen Johansen
2008-04-22 7:48 ` Junio C Hamano
2008-04-24 5:39 ` Sverre Hvammen Johansen [this message]
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=402c10cd0804232239p3e49a6d0vdc1ff9acb3636a17@mail.gmail.com \
--to=hvammen@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).