From: Elijah Newren <newren@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Jeff King <peff@peff.net>
Subject: Re: What's cooking in git.git (Jun 2011, #02; Sat, 11)
Date: Mon, 13 Jun 2011 22:27:50 -0600 [thread overview]
Message-ID: <BANLkTin-sAXAZ4ZJ9z77SSYx+xYTYeZMww@mail.gmail.com> (raw)
In-Reply-To: <7voc23sfxd.fsf@alter.siamese.dyndns.org>
Hi,
On Sun, Jun 12, 2011 at 12:49 AM, Junio C Hamano <gitster@pobox.com> wrote:
> Here are the topics that have been cooking. Commits prefixed with '-' are
> only in 'pu' while commits prefixed with '+' are in 'next'.
>
> --------------------------------------------------
> [Stalled]
>
> * jk/maint-merge-rename-create (2011-03-25) 3 commits
> - merge: turn on rewrite detection
> - merge: handle renames with replacement content
> - t3030: fix accidental success in symlink rename
>
> Peff wanted to reroll this. Perhaps will discard to make room for Elijah's
> merge-recursive series in the meantime.
Peff: Do you want any help rerolling, updating, reviewing, etc.? I
don't want to cause any undue problems with my merge-recursive series,
and besides, the idea you have in this series looks like it may be
interesting.
next prev parent reply other threads:[~2011-06-14 4:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-12 6:49 What's cooking in git.git (Jun 2011, #02; Sat, 11) Junio C Hamano
2011-06-12 12:14 ` Ramkumar Ramachandra
2011-06-13 0:17 ` "libify part of reset" mini-series (Re: What's cooking in git.git (Jun 2011, #02; Sat, 11)) Jonathan Nieder
2011-06-13 13:16 ` What's cooking in git.git (Jun 2011, #02; Sat, 11) Junio C Hamano
2011-06-12 16:18 ` Sverre Rabbelier
2011-06-13 15:25 ` Junio C Hamano
2011-06-13 16:07 ` Sverre Rabbelier
2011-06-14 4:27 ` Elijah Newren [this message]
2011-06-16 21:05 ` Jeff King
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=BANLkTin-sAXAZ4ZJ9z77SSYx+xYTYeZMww@mail.gmail.com \
--to=newren@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
/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).