Duy Nguyen pclo...@gmail.com writes:
I worry less about this. It's not the right model to have two machines
modify the same shared repository (gc --auto is only triggered when we
think there are new objects) even though I think we support it.
I am a bit hesitant to dismiss with It's not the
Junio C Hamano wrote:
I am a bit hesitant to dismiss with It's not the right model, as
the original of accessing the repository from two terminals while
one clearly is being accessed busily by gc falls into the same
category.
As to why I think it makes sense: garbage collecting unreferenced
Martin Fick wrote:
https://gerrit-review.googlesource.com/#/c/35215/
Very cool. Of what I understood:
So, the problem is that my .git/objects/pack is polluted with little
packs everytime I fetch (or push, if you're the server), and this is
problematic from the perspective of a overtly (naively)
On Monday, August 05, 2013 11:34:24 am Ramkumar Ramachandra
wrote:
Martin Fick wrote:
https://gerrit-review.googlesource.com/#/c/35215/
Very cool. Of what I understood:
So, the problem is that my .git/objects/pack is polluted
with little packs everytime I fetch (or push, if you're
the
Martin Fick wrote:
I hope
that someone more familiar with git gc than me might take
this on some day. :)
More likely scenario: someone who is unfamiliar with it will read and
patch it little by little :)
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message
Hi,
I was pulling in some changes in the morning to find:
Auto packing the repository for optimum performance. You may also
run git gc manually. See git help gc for more information.
Being my usual impatient self, I opened another prompt and started
merging changes. After the checkout, it
On Sat, Aug 3, 2013 at 8:48 AM, Ramkumar Ramachandra artag...@gmail.com wrote:
Auto packing the repository for optimum performance. You may also
run git gc manually. See git help gc for more information.
Being my usual impatient self, I opened another prompt and started
merging changes.
On Fri, Aug 2, 2013 at 8:53 PM, Duy Nguyen pclo...@gmail.com wrote:
Good point. I think that is because gc does not check if gc is already
running. Adding such a check should not be too hard. I think gc could
save its pid in $GIT_DIR/auto-gc.pid. The next auto-gc checks this, if
the pid is
8 matches
Mail list logo
