All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yann Dirson <ydirson@free.fr>
To: Erik Faye-Lund <kusmabite@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Nov 2010, #01; Tue, 9)
Date: Wed, 10 Nov 2010 21:35:16 +0100	[thread overview]
Message-ID: <20101110203516.GE8911@home.lan> (raw)
In-Reply-To: <AANLkTi=F6768YZdR4H-vcnHgknV=roHG249dzbNRJVXR@mail.gmail.com>

On Tue, Nov 09, 2010 at 11:17:07PM +0100, Erik Faye-Lund wrote:
> On Tue, Nov 9, 2010 at 8:53 PM, Junio C Hamano <gitster@pobox.com> wrote:
> > * yd/dir-rename (2010-10-29) 5 commits
> >  - Allow hiding renames of individual files involved in a directory rename.
> >  - Unified diff output format for bulk moves.
> >  - Add testcases for the --detect-bulk-moves diffcore flag.
> >  - Raw diff output format for bulk moves.
> >  - Introduce bulk-move detection in diffcore.
> >
> 
> This series currently breaks the Windows build of 'pu', as we lack
> memrchr there. Jonathan Nieder posted a patch
> (<20101015051750.GA21830@burratino>) that adds a memrchr
> implementation. This should probably either be rebased on top of that
> patch, or re-rolled.
> 
> While 'pu' not building on Windows might not be a big deal, it's worth
> keeping in mind before merging it further.

If you plan to re-roll the series as it is, you may want to consider
the latest update to the 1st patch in the series.  I had not resent
the whole series just for that.

http://marc.info/?l=git&m=128890797304674

OTOH, you may want to wait for the next iteration, which should be
ready by the end of the week.

  parent reply	other threads:[~2010-11-10 20:35 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-09 19:53 What's cooking in git.git (Nov 2010, #01; Tue, 9) Junio C Hamano
2010-11-09 20:11 ` Ævar Arnfjörð Bjarmason
2010-11-09 20:19 ` Matthieu Moy
2010-11-09 20:29   ` Drew Northup
2010-11-09 20:38 ` Jonathan Nieder
2010-11-09 21:38 ` Jakub Narebski
2010-11-11 17:21   ` Junio C Hamano
2010-11-11 23:53     ` Jakub Narebski
2010-11-09 21:46 ` Johan Herland
2010-11-09 22:11 ` Jeff King
2010-11-09 22:17 ` Erik Faye-Lund
2010-11-09 22:21   ` Ævar Arnfjörð Bjarmason
2010-11-09 22:25     ` Erik Faye-Lund
2010-11-09 22:27       ` Ævar Arnfjörð Bjarmason
2010-11-10 20:35   ` Yann Dirson [this message]
2010-11-11 12:26 ` Nguyen Thai Ngoc Duy
2010-11-11 14:28 ` Nguyen Thai Ngoc Duy
2010-11-14 13:02 ` [PATCH] use persistent memory for rejected paths Clemens Buchacher
2010-11-15 18:31   ` Junio C Hamano
2010-11-15 19:02     ` Clemens Buchacher
2010-11-15 19:03   ` Matthieu Moy
2010-11-15 19:41     ` Clemens Buchacher
2010-11-15 19:52       ` [PATCH v2] " Clemens Buchacher
2010-11-16 16:41         ` Matthieu Moy
2010-11-15 23:05       ` [PATCH] " Junio C Hamano
2010-11-15 23:30         ` Clemens Buchacher

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=20101110203516.GE8911@home.lan \
    --to=ydirson@free.fr \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=kusmabite@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.