From: Johan 't Hart <johanthart@gmail.com>
To: git@vger.kernel.org
Cc: git@vger.kernel.org
Subject: Re: git-svn mergeinfo support performance problem
Date: Sun, 20 Dec 2009 01:28:32 +0100 [thread overview]
Message-ID: <4B2D6FB0.6080103@gmail.com> (raw)
In-Reply-To: <6b2f9b1d0912181708g32645b48j3886b74101e77d80@mail.gmail.com>
Andrew Myrick schreef:
> I've been testing git-svn v1.6.6-rc3's mergeinfo support on a large
> svn repository (60,000+ revisions, 20+ GiB) that uses a very
> branch-heavy integration model in which every change gets its own
> branch before being committed to trunk. As a result of the model,
> there are currently over 1000 lines in the svn:mergeinfo property on
> trunk.
Just wondering: Isnt this workflow stalling svn itself alot too?
And also:
Do you delete the branches after you reintegrated them? If so, I think
its safe for you to cleanup the svn mergeinfo once in a while. That
should not affect 'svn log -g' because the mergeinfo is still there in
older revisions. I think svn benefits from this too...
next prev parent reply other threads:[~2009-12-20 0:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-19 1:08 git-svn mergeinfo support performance problem Andrew Myrick
2009-12-20 0:28 ` Johan 't Hart [this message]
2009-12-20 0:39 ` Andrew Myrick
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=4B2D6FB0.6080103@gmail.com \
--to=johanthart@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.