Hello everyone,
I am trying to find some official information about the limit size of a
repository. As I have read git has a limitation of 2GB for each repo
because if you increment the size it starts to decrease the overall
performance. But this limitation is mainly explained in the web based
On Tue, Dec 26, 2017 at 05:54:21PM -, Philip Oakley wrote:
> The key points were that bisect will search *all* heirarchy paths (unless
> you tell it different). This means that all side heirarchies are also places
> that bisect will search.
>
> Each time you give a 'good' history point it will
Git does not have a limitation of 2 GB for each repo. I don't think you'll
find official information about the limits on repository size except in the
context of specific use cases (like gitweb, GitHub, BitBucket, Gitlab, etc.)
At a previous employer, we regularly worked with a repository that wa
On Wed, Dec 27, 2017 at 12:08:07AM -0800,
antonio.poma...@external.thalesgroup.com wrote:
> I am trying to find some official information about the limit size of a
> repository. As I have read git has a limitation of 2GB for each repo
> because if you increment the size it starts to decrease th
Hi Marc,
Found the reference article about 'git describe' and the way commits can
'bypass' (or appear to) the expected tags.
https://public-inbox.org/git/20140422040443.gc9...@odin.tremily.us/ shows the
discussion which started at
https://public-inbox.org/git/1397681938-18594-1-git-send-email-
Oh, I was wrong about 'git bisect' actually allowing --first parent (it was
just an expectation ;-),
Though it should, based on a quick search for 'git bisect --first-parent'
which gives quite a few mini-scripts to create the appropriate 'good'
commit list to see where the defect was merged i
