From: Nazri Ramliy <ayiehere@gmail.com>
To: Thomas Rast <trast@inf.ethz.ch>
Cc: Zhan Jianyu <nasa4836@gmail.com>, Git Mailing List <git@vger.kernel.org>
Subject: Re: Does Git now have any C struct version history tracking mechanism?
Date: Tue, 20 Aug 2013 11:55:17 +0800 [thread overview]
Message-ID: <CAEY4ZpM6U38piim_uY5KgaZX=1KkYF4WaMxR9HeywAp4AO9igw@mail.gmail.com> (raw)
In-Reply-To: <87y57y84a1.fsf@linux-k42r.v.cablecom.net>
On Mon, Aug 19, 2013 at 4:37 PM, Thomas Rast <trast@inf.ethz.ch> wrote:
> Hmm, IIUC that's actually not a bug or even a roughness; it's an
> artifact of how the :pattern:file syntax is defined. It takes the first
> _funcname line_ matching 'pattern', up to (but excluding) the next
> funcname line.
>
...
> Or is there an issue that I'm missing?
No you're correct. I should have used the following instead for the demo:
$ git log -L /struct\ rev_cmdline_info/,/^}/:revision.h
Moral: You'd hit your target better if you work on your aim.
nazri
prev parent reply other threads:[~2013-08-20 3:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-18 10:33 Does Git now have any C struct version history tracking mechanism? Zhan Jianyu
2013-08-19 5:54 ` Nazri Ramliy
2013-08-19 8:37 ` Thomas Rast
2013-08-20 3:55 ` Nazri Ramliy [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='CAEY4ZpM6U38piim_uY5KgaZX=1KkYF4WaMxR9HeywAp4AO9igw@mail.gmail.com' \
--to=ayiehere@gmail.com \
--cc=git@vger.kernel.org \
--cc=nasa4836@gmail.com \
--cc=trast@inf.ethz.ch \
/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).