From: Junio C Hamano <gitster@pobox.com>
To: Jonathon Mah <me@JonathonMah.com>
Cc: Dan McGee <dpmcgee@gmail.com>, David Aguilar <davvid@gmail.com>,
git@vger.kernel.org
Subject: Re: What's cooking in git.git (Sep 2011, #04; Mon, 12)
Date: Wed, 14 Sep 2011 13:57:38 -0700 [thread overview]
Message-ID: <7vsjnysuyl.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <D3CA81F2-647B-4AD0-A4FC-4C22772FD791@JonathonMah.com> (Jonathon Mah's message of "Tue, 13 Sep 2011 19:34:18 -0700")
Jonathon Mah <me@JonathonMah.com> writes:
> On 2011-09-12, at 14:59, Junio C Hamano wrote:
>
>>> [Stalled]
>>>
>>> * jm/mergetool-pathspec (2011-06-22) 2 commits
>>> - mergetool: Don't assume paths are unmerged
>>> - mergetool: Add tests for filename with whitespace
>>
>> What's the plan for this series? Do we still want to pursue it within the
>> timeframe for the next round?
>>
>> Is there any mergetool/difftool expert who volunteers to help moving this
>> topic forward?
>
> I'd love this to stay alive. As I've mentioned before, my relationship
> with shell is tenuous. My biggest problem is...
Hopefully volunteers can help moving this forward with "coding".
http://thread.gmane.org/gmane.comp.version-control.git/176215
http://thread.gmane.org/gmane.comp.version-control.git/176216
There were issues with the patches that were _not_ about the coding but
about the documentation and design.
Topics with a stale version in 'pu' that are stalled are not even alive--
they are zombies that need to be wiped at some point, or replaced with
updated series, whichever comes first.
next prev parent reply other threads:[~2011-09-14 20:57 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-12 20:16 What's cooking in git.git (Sep 2011, #04; Mon, 12) Junio C Hamano
2011-09-12 21:48 ` Junio C Hamano
2011-09-12 21:51 ` Junio C Hamano
2011-09-12 23:27 ` Jeff King
2011-09-13 0:09 ` Junio C Hamano
2011-09-13 9:24 ` Nguyen Thai Ngoc Duy
2011-09-12 21:53 ` Junio C Hamano
2011-09-13 7:32 ` [PATCH v2] Documentation: basic configuration of notes.rewriteRef Thomas Rast
2011-09-13 17:16 ` Junio C Hamano
2011-09-13 17:18 ` Jeff King
2011-09-12 21:55 ` What's cooking in git.git (Sep 2011, #04; Mon, 12) Junio C Hamano
2011-09-12 21:59 ` Junio C Hamano
2011-09-14 2:34 ` Jonathon Mah
2011-09-14 20:57 ` Junio C Hamano [this message]
2011-09-16 2:12 ` [PATCH] mergetool: Use args as pathspec to unmerged files Jonathon Mah
2011-09-16 20:17 ` Junio C Hamano
2011-09-25 0:45 ` David Aguilar
2011-09-26 16:40 ` Junio C Hamano
2011-09-12 22:02 ` What's cooking in git.git (Sep 2011, #04; Mon, 12) Junio C Hamano
2011-09-12 23:15 ` Sverre Rabbelier
2011-09-12 22:56 ` Junio C Hamano
2011-09-13 9:46 ` Erik Faye-Lund
2011-09-29 12:03 ` Pascal Obry
2011-09-12 22:58 ` Junio C Hamano
2011-09-13 12:05 ` Michael J Gruber
[not found] ` <7vk49d5t8u.fsf@alter.siamese.dyndns.org>
2011-09-12 23:15 ` Eric Sunshine
2011-09-12 23:25 ` Junio C Hamano
2011-09-12 23:33 ` Jeff King
2011-09-12 23:53 ` Jeff King
2011-09-13 15:15 ` Brandon Casey
2011-09-13 16:05 ` Jeff King
2011-09-13 16:22 ` Brandon Casey
2011-09-13 7:51 ` John Szakmeister
2011-09-13 15:04 ` Eric Sunshine
2011-09-13 17:20 ` Jeff King
2011-09-12 23:35 ` Junio C Hamano
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=7vsjnysuyl.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=davvid@gmail.com \
--cc=dpmcgee@gmail.com \
--cc=git@vger.kernel.org \
--cc=me@JonathonMah.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).