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

2009/3/24 Johannes Schindelin <Johannes.Schindelin@gmx.de>:
>> 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).
>
> Did I miss something?  git ls-files pipes only the names to xargs, not the
> full contents, right?

See where I wrote "this kind of pipeline" vs "git ls-files" which was
just quoting Peff? 8-)

I dunno, maybe C folk using git would only be interested in the
index/working copy, but that tells me this script is even more
tenuously linked to git. We don't bundle a compiler just because it
can use git ls-files to work out what to compile...

The script might be best as a standalone tool which just happened to
take advantage of the VCS in use by reacting to its surroundings. Then
it would also be useful by hg, svn, cvs people etc.

If it actually used the information in the repository to be able to
run git blame on the definitions, or show a git log -p style list of
changes in the definition, that might be different.

Mike

  reply	other threads:[~2009-03-24 16:39 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 [this message]
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=e2b179460903240937p58dff7e8u238fbe06785cdb77@mail.gmail.com \
    --to=mike.ralphson@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=orthochronous@gmail.com \
    --cc=peff@peff.net \
    --cc=pkufranky@gmail.com \
    --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).