git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Tweed <orthochronous@gmail.com>
To: Mike Ralphson <mike.ralphson@gmail.com>
Cc: Jeff King <peff@peff.net>, Roel Kluin <roel.kluin@gmail.com>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	git@vger.kernel.org
Subject: Re: [PATCH] git-cget: prints elements of C code in the git repository
Date: Tue, 24 Mar 2009 16:33:13 +0000	[thread overview]
Message-ID: <d9c1caea0903240933n6dea7ddcl90a5e105c2a45b52@mail.gmail.com> (raw)
In-Reply-To: <e2b179460903240738x272c884q62a666931ce99c2f@mail.gmail.com>

On Tue, Mar 24, 2009 at 2:38 PM, Mike Ralphson <mike.ralphson@gmail.com> wrote:
> 2009/3/24 Jeff King <peff@peff.net>:
> This kind of pipeline has the benefit that it can actually work on the
> *repository*, and not just the working copy (as per the posted
> script).

Speaking of wanting things to work with the actual repository , one
thing that I've been meaning to continue work on if I get the time is
basically a 'show me any commit diff's that involve string s' (ie, the
locations in which a change involving s occurs rather than just
'current file contains s (in exactly the same ways the previous
version did). I'm extremely unlikely to actually produce anything
based on that in the near future. But one thing that struck me that
might be reasonably useful is some way of filtering the "context" that
a string occurs in (is it in generic code context, in a string or in a
comment). These are things that tend to be reasonably parametrisable
by regular expressions (although escaping string delimiters within in
strings makes completely correct behaviour tricky), so if git-grep
itself were to be extended I'd prefer something that can be specified
per search in a more generally usable way than something very C
specific. Of course this is a quite difficult task as the actual diff
may not contain enough lines to distinguish, eg, that it occurs within
a longer comment. (As already disclaimed, I'm unlikely to actually get
around to doing any of this work).

cheers, dave tweed

  parent reply	other threads:[~2009-03-24 16:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-24 10:09 [PATCH] git-cget: prints elements of C code in the git repository Roel Kluin
2009-03-24 12:05 ` Johannes Schindelin
2009-03-24 13:30   ` Roel Kluin
2009-03-24 13:52     ` Johannes Schindelin
2009-03-24 15:08       ` Ping Yin
2009-03-24 13:59     ` Jeff King
2009-03-24 14:04       ` Stefan Karpinski
2009-03-24 14:05       ` Johannes Schindelin
2009-03-24 14:38       ` Mike Ralphson
2009-03-24 14:56         ` Johannes Schindelin
2009-03-24 16:37           ` Mike Ralphson
2009-03-24 16:33         ` Steven Tweed [this message]
2009-03-25  4:23           ` Jeff King
2009-03-24 16:17       ` roel kluin
2009-03-27  9:22   ` roel kluin
2009-03-27 11:26     ` Johannes Schindelin

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=d9c1caea0903240933n6dea7ddcl90a5e105c2a45b52@mail.gmail.com \
    --to=orthochronous@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=mike.ralphson@gmail.com \
    --cc=peff@peff.net \
    --cc=roel.kluin@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 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).