On 31 May 2013 10:57, Alex Bennée <kernel-hac...@bennee.com> wrote:
> On 31 May 2013 09:46, Thomas Rast <tr...@inf.ethz.ch> wrote:
>> So that deleted all unannotated tags pointing at commits, and then it
>> was fast. Curious.
>> However, if that turns out to be the culprit, it's not fixable
>> currently. Having commits with insanely long messages is just, well,
>>  unless we do a major rework of the loading infrastructure, so that
>> we can teach it to load only the beginning of a commit as long as we are
>> only interested in parents and such
> I'll do a bit of scripting to dig into the nature of these
> uber-commits and try and work out how they cam about. I suspect they
> are simply start of branch states in our broken and disparate history.
> I'll get back to you once I've dug a little deeper.
So I wrote a little script  which I ran to remove all tags that did
not exist on any branches:
git-tag-cleaner.py -d no-branch
After a lot of churning:
17:26 ajb@sloy/x86_64 [work.git] >time /usr/bin/git --no-pager
describe --long --tags
So at least I can fix up my repo. All the big ones look at least as
though they were weird cvs2svn creations that exist to represent the
detached state of a strange CVS tag from the converted repository.
However it does raise one question.
Why is git attempting to parse a commit not on the DAG for the branch
I'm attempting to describe?
Anyway as I have a work around I'm going to do a slightly more
conservative clean of the repo with my script and move on.
Alex, homepage: http://www.bennee.com/~alex/
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html