Excerpts from Thierry Goubier's message of 2015-03-09 13:13:23 +0100:
> There is technical limitations in adding that information (or using it). I
> did use it a long time ago at the beginning of gitfiletree, but it was
> prohibitively slow, even on small git repositories.
i find this puzzling. wh
2015-03-09 11:39 GMT+01:00 Sean P. DeNigris :
> Martin Bähr wrote
> >> It takes ages to scan the version metadata contained in the git
> >> repository.
> > why is that?
>
> Also, this is a copy operation, so we already have the version number from
> the mcz! Why can't we just use that?
>
No probl
Martin Bähr wrote
>> It takes ages to scan the version metadata contained in the git
>> repository.
> why is that?
Also, this is a copy operation, so we already have the version number from
the mcz! Why can't we just use that?
-
Cheers,
Sean
--
View this message in context:
http://forum.wo
Excerpts from Thierry Goubier's message of 2015-03-09 07:06:41 +0100:
> Le 09/03/2015 04:20, Sean P. DeNigris a écrit :
> > When copying MyPackage-Author-VersionNumber.mcz to an empty GitFileTree
> > repository, VersionNumber is not considered, and it appears in the version
> > browser as MyPackage
Le 09/03/2015 04:20, Sean P. DeNigris a écrit :
When copying MyPackage-Author-VersionNumber.mcz to an empty GitFileTree
repository, VersionNumber is not considered, and it appears in the version
browser as MyPackage-Author-1, which seems confusing. Could it keep the same
VersionNumber?
No ;)
I
