Hello,
cc'ing Roman, the original author. (I should have done that
in the first post, sorry. I have also forwarded him another
mail from this thread, asking him for author's sign off.)
On Thu, Apr 17, 2014 at 10:39:49AM -0700, Junio C Hamano wrote:
> Stepan Kasal writes:
>
> > On Wed, Apr 16,
Stepan Kasal writes:
> From: RomanBelinsky
> Date: Tue, 11 Feb 2014 18:23:02 +0200
>
> fix parsing error for dates like:
> 2014-01-07T5:58:36.048176Z
> previous regex can parse only:
> 2014-01-07T05:58:36.048176Z
> reproduced in my svn repository during conversion.
>
> Signed-off-by: Stepan Kasa
Stepan Kasal writes:
> On Wed, Apr 16, 2014 at 12:13:21PM -0700, Junio C Hamano wrote:
>> Interesting. What other strange forms can they record in their
>> repositories, I have to wonder. Can they do
>> 2014-01-07T5:8:6.048176Z
>> for example?
>
> Roman Belinsky, the author of this fix, wit
Hello,
On Wed, Apr 16, 2014 at 12:13:21PM -0700, Junio C Hamano wrote:
> Interesting. What other strange forms can they record in their
> repositories, I have to wonder. Can they do
> 2014-01-07T5:8:6.048176Z
> for example?
Roman Belinsky, the author of this fix, witnessed after large scale
Stepan Kasal writes:
> From: RomanBelinsky
> Date: Tue, 11 Feb 2014 18:23:02 +0200
>
> fix parsing error for dates like:
> 2014-01-07T5:58:36.048176Z
> previous regex can parse only:
> 2014-01-07T05:58:36.048176Z
> reproduced in my svn repository during conversion.
Interesting. What other stra
From: RomanBelinsky
Date: Tue, 11 Feb 2014 18:23:02 +0200
fix parsing error for dates like:
2014-01-07T5:58:36.048176Z
previous regex can parse only:
2014-01-07T05:58:36.048176Z
reproduced in my svn repository during conversion.
Signed-off-by: Stepan Kasal
---
perl/Git/SVN.pm | 2 +-
1 file ch
6 matches
Mail list logo
