Heya, [+shawn, who runs into something similar with Gerrit] On Thu, Jun 9, 2011 at 05:44, NAKAMURA Takumi <geek4civic@xxxxxxxxx> wrote: > Hello, Git. It is my 1st post here. > > I have tried tagging each commit as "refs/tags/rXXXXXX" on git-svn > repo locally. (over 100k refs/tags.) > Indeed, it made something extremely slower, even with packed-refs and > pack objects. > I gave up, then, to push tags to upstream. (it must be terror) :p > > I know it might be crazy in the git way, but it would bring me conveniences. > (eg. git log --oneline --decorate shows me each svn revision) > I would like to work for Git to live with many tags. > > * Issues as far as I have investigated; > > Â- git show --decorate is always slow. > Â Âin decorate.c, every commits are inspected. > Â- git rev-tree --quiet --objects $upstream --not --all spends so much time, > Â Âeven if it is expected to return with 0. > Â ÂAs you know, it is used in builtin/fetch.c. > Â- git-upload-pack shows "all" refs to me if upstream has too many refs. > > I would like to work as below if they were valuable. > > Â- Get rid of inspecting commits in packed-refs on decorate stuff. > Â- Implement sort-by-hash packed-refs, (not sort-by-name) > Â- Implement more effective pruning --not --all on revision.c. > Â- Think about enhancement of protocol to transfer many refs more effectively. > > I am happy to consider the issue, thank you. -- Cheers, Sverre Rabbelier -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html