From: Thomas Rast <trast@student•ethz.ch>
To: Junio C Hamano <gitster@pobox•com>
Cc: "Jeff King" <peff@peff•net>,
git@vger•kernel.org, "Philip Oakley" <philipoakley@iee•org>,
"Jonathan Nieder" <jrnieder@gmail•com>,
"Nguyễn Thái Ngọc Duy" <pclouds@gmail•com>,
"Matthew Blissett" <matt@blissett•me.uk>,
"David Aguilar" <davvid@gmail•com>,
"John Keeping" <john@keeping•me.uk>,
"Johannes Sixt" <j6t@kdbg•org>
Subject: Re: What's cooking in git.git (Mar 2013, #07; Tue, 26)
Date: Thu, 28 Mar 2013 09:00:17 +0100 [thread overview]
Message-ID: <87ehf0uf72.fsf@linux-k42r.v.cablecom.net> (raw)
In-Reply-To: <7vy5d8jz0y.fsf@alter.siamese.dyndns.org> (Junio C. Hamano's message of "Wed, 27 Mar 2013 14:47:25 -0700")
Junio C Hamano <gitster@pobox•com> writes:
>> * tr/line-log (2013-03-23) 6 commits
>> - Speed up log -L... -M
>> - log -L: :pattern:file syntax to find by funcname
>> - Implement line-history search (git log -L)
>> - Export rewrite_parents() for 'log -L'
>> - fixup
>> - Refactor parse_loc
>>
>> Rerolled; collides with nd/magic-pathspecs.
>
> Honestly I am not sure what to make of this one. I'd say we should
> merge this down as-is to 'master', expecting that in some future we
> would fix "log --follow" to keep the refspecs per history traversal
> path, so that this can be more naturally reimplemented. Objections?
I was really hoping for something like that to happen :-) but I need to
look into at least one segfault bug in the option parser, noticed by
Antoine Pelisse. Expect a (final?) reroll soon.
--
Thomas Rast
trast@{inf,student}.ethz.ch
prev parent reply other threads:[~2013-03-28 8:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-26 22:40 What's cooking in git.git (Mar 2013, #07; Tue, 26) Junio C Hamano
2013-03-27 20:35 ` Jeff King
2013-03-27 20:50 ` Junio C Hamano
2013-03-27 20:52 ` Jeff King
2013-03-27 20:50 ` Thomas Rast
2013-03-27 21:47 ` Junio C Hamano
2013-03-27 22:07 ` John Keeping
2013-03-27 22:15 ` Junio C Hamano
2013-03-27 22:52 ` John Keeping
2013-03-28 21:40 ` Junio C Hamano
2013-03-27 22:25 ` jn/add-2.0-u-A-sans-pathspec (Re: What's cooking in git.git (Mar 2013, #07; Tue, 26)) Jonathan Nieder
2013-03-28 8:00 ` Thomas Rast [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=87ehf0uf72.fsf@linux-k42r.v.cablecom.net \
--to=trast@student$(echo .)ethz.ch \
--cc=davvid@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=j6t@kdbg$(echo .)org \
--cc=john@keeping$(echo .)me.uk \
--cc=jrnieder@gmail$(echo .)com \
--cc=matt@blissett$(echo .)me.uk \
--cc=pclouds@gmail$(echo .)com \
--cc=peff@peff$(echo .)net \
--cc=philipoakley@iee$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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