From: Andy Whitcroft <apw@shadowen.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] cvsimport move over to using git for each ref to read refs
Date: Wed, 20 Sep 2006 17:12:56 +0100 [thread overview]
Message-ID: <45116888.4050806@shadowen.org> (raw)
In-Reply-To: <7vodtak00n.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
> Andy Whitcroft <apw@shadowen.org> writes:
>
>> I guess we could teach for-each-ref to output this as well? Perhaps
>> something like authorstamp?
>
> I think you can work with "author" or "committer" to grab the
> whole raw line.
>
> About the quoting and parsing, language specific quoting mode is
> meant for git-for-each-ref to produce a string that can be eval'ed
> in the host language. Think of the command as a tool to write a
> short program for you.
Thanks for the education. Very simple, and very powerful. I knew there
was a reason for it out there. Will respin a V3 patch in a bit.
-apw
next prev parent reply other threads:[~2006-09-20 16:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-20 8:52 [PATCH] cvsimport move over to using git for each ref to read refs Andy Whitcroft
2006-09-20 9:23 ` Jakub Narebski
2006-09-20 10:26 ` Andy Whitcroft
2006-09-20 10:31 ` [PATCH 1/2] for each ref add a raw timestamp field type Andy Whitcroft
2006-09-20 10:31 ` [PATCH 2/2] cvsimport move over to using git for each ref to read refs V2 Andy Whitcroft
2006-09-20 11:00 ` [PATCH] cvsimport move over to using git for each ref to read refs Jakub Narebski
2006-09-20 15:53 ` Junio C Hamano
2006-09-20 16:12 ` Andy Whitcroft [this message]
2006-09-20 16:37 ` [PATCH] cvsimport move over to using git for each ref to read refs V3 Andy Whitcroft
2006-09-20 16:55 ` Junio C Hamano
2006-09-20 17:00 ` Andy Whitcroft
2006-09-20 17:17 ` Junio C Hamano
2006-09-20 16:45 ` [PATCH] cvsimport move over to using git for each ref to read refs Junio C Hamano
2006-09-21 12:06 ` Andy Whitcroft
2006-09-22 4:57 ` Junio C Hamano
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=45116888.4050806@shadowen.org \
--to=apw@shadowen.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).