From: Sam Vilain <sam@vilain.net>
To: git@vger.kernel.org
Subject: Re: [PATCH 2/4] git-svn: collect SVK source URL on mirror paths
Date: Tue, 05 Dec 2006 13:39:48 +1100 [thread overview]
Message-ID: <4574DBF4.8010007@vilain.net> (raw)
In-Reply-To: <20061204235724.5393E1380C2@magnus.utsl.gen.nz>
Sam Vilain wrote:
> + my $uuid = $props->{'svm:uuid'};
> + $uuid =~ m{^[0-9a-f\-]{41,}}
> + or croak "doesn't look right - svm:uuid is '$uuid'";
This joke back-fired. 41 is too long; UUIDs just *look* longer than
SHA1's :). "36" seems a more appropriate value...
prev parent reply other threads:[~2006-12-05 2:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-04 9:35 [PATCH 2/4] git-svn: collect SVK source URL on mirror paths Sam Vilain
2006-12-05 2:39 ` Sam Vilain [this message]
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=4574DBF4.8010007@vilain.net \
--to=sam@vilain.net \
--cc=git@vger.kernel.org \
/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).