From: Andy Whitcroft <apw@shadowen.org>
To: Jakub Narebski <jnareb@gmail.com>
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 11:26:05 +0100 [thread overview]
Message-ID: <4511173D.7020702@shadowen.org> (raw)
In-Reply-To: <eer19l$6hm$1@sea.gmane.org>
Jakub Narebski wrote:
> Andy Whitcroft wrote:
>
>> + open(H, "git-for-each-ref --format='%(objectname) %(refname)'|") or
>
> By the way, this is equivalent to using "git-show-ref" introduced by Linus.
> But if you want commit timestamp
>
>> cvsimport opens all of the files in $GIT_DIR/refs/heads and reads
>> out the sha1's in order to work out what time the last commit on
>> that branch was made (in CVS) thus allowing incremental updates.
>
> you can use it in --format as well.
Unfortuantly, for-each-ref only offers us the textual version of this
information not the numeric offset from the epoch which is what
cvsimport is after.
I guess we could teach for-each-ref to output this as well? Perhaps
something like authorstamp?
-apw
next prev parent reply other threads:[~2006-09-20 10:26 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 [this message]
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
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=4511173D.7020702@shadowen.org \
--to=apw@shadowen.org \
--cc=git@vger.kernel.org \
--cc=jnareb@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).