git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ping Yin <pkufranky@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Roel Kluin <roel.kluin@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH] git-cget: prints elements of C code in the git repository
Date: Tue, 24 Mar 2009 23:08:01 +0800	[thread overview]
Message-ID: <46dff0320903240808p5ad287d8j9245ee9f79ff6851@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0903241449200.7493@intel-tinevez-2-302>

On Tue, Mar 24, 2009 at 9:52 PM, Johannes Schindelin
<Johannes.Schindelin@gmx.de> wrote:

>> Also, what would be more appropriate for this purpose, I think, is a git
>> sed.
>
> Just as it happens, this is a toy I am working on and off these days...
> strbuf_regsub() is already done, and half the needed code is in my version
> git grep.
>

this is my version

[alias]
sed = !git ls-files --stage | grep ^100 | awk '{print $4}' | xargs sed

Then i can do

git sed -i 's/A/B/g'

  reply	other threads:[~2009-03-24 15:09 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 [this message]
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
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=46dff0320903240808p5ad287d8j9245ee9f79ff6851@mail.gmail.com \
    --to=pkufranky@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --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).