From: Jonas Fonseca Date: Wed, 07 Dec 2005 21:40:13 GMT Subject: [PATCH] cg-object-id: use git-rev-parse(1) for date parsing Message-ID: <20051207214013.GD25890@diku.dk> Using the --until switch, git-rev-parse(1) will first be given the ID. If it cannot make sense of the ID fallback to using date(1). Signed-off-by: Jonas Fonseca --- The mixing of date parsing behaviours might be a little questionable, but it's good to stay compatible with git. commit 41447107236a7d23daa6ab0f40a0829935485bc8 tree 27863684c19e7f129304d2a1573c08f974126e2a parent f0535e9952f1cace89d03649e8238aca69a6df44 author Jonas Fonseca Wed, 07 Dec 2005 22:16:50 +0100 committer Jonas Fonseca Wed, 07 Dec 2005 22:16:50 +0100 cg-object-id | 9 ++++++++- 1 files changed, 8 insertions(+), 1 deletions(-) diff --git a/cg-object-id b/cg-object-id index ea04dca..baf096e 100755 --- a/cg-object-id +++ b/cg-object-id @@ -73,7 +73,14 @@ normalize_id() fi if [ "$id" != " " ] && [ ! "$valid" ]; then - reqsecs=$(date --date="$id" +'%s' 2>/dev/null) + curtime=$(date +'%s' 2>/dev/null) + reqsecs=$(git-rev-parse --until="$id"); reqsecs=${reqsecs:10} + + # git-rev-parse(1) will output the current time if the ID + # doesn't make sense. Workaround it so date(1) can have a try. + if [ "$curtime" -le "$reqsecs" ]; then + reqsecs=$(date --date="$id" +'%s' 2>/dev/null) + fi if [ "$reqsecs" ]; then id=$(git-rev-list --min-age=$reqsecs --max-count=1 HEAD) -- Jonas Fonseca