If I push straight to the other repo, it only pushes the 3 objects I'd
expect (instead of 10,000+). So it looks like that is the problem, but
I don't really understand why.
>From my point of view, there should be no difference, but I clearly
don't understand how it actually works. How does git dec
On Mon, Mar 23, 2015 at 5:35 PM, Graham Hay wrote:
> Hmm. I'm using a "private" fork of a repo, I pull from one and push to
> the other, e.g.
>
> git fetch foo
> git rebase foo/master
> git push --set-upstream origin bar
>
> It's quite possible my workflow is causing the problem, but I'm not
> sur
Hmm. I'm using a "private" fork of a repo, I pull from one and push to
the other, e.g.
git fetch foo
git rebase foo/master
git push --set-upstream origin bar
It's quite possible my workflow is causing the problem, but I'm not
sure what I could do differently. What do you mean by a "no-share
remot
On Thu, Mar 19, 2015 at 6:11 PM, Graham Hay wrote:
>> Try "fast-export --anonymize" as that would help us understand this.
>
> Attached.
The bad news is it seems to be working for me (I recreated the remote
repo from this dump). I notice that you have two remotes, one shares
many refs (the remote
That all seems quite reasonable, and is what I would expect to happen.
However at the moment, if I create a branch from master and edit one
line in one file,
with no other changes on the remote, it takes me over an hour to push
the new branch.
On 19 March 2015 at 18:36, Junio C Hamano wrote:
> G
Graham Hay writes:
> We have a fairly large repo (~2.4GB), mainly due to binary resources
> (for an ios app). I know this can generally be a problem, but I have a
> specific question.
>
> If I cut a branch, and edit a few (non-binary) files, and push, what
> should be uploaded? I assumed it was j
On Wed, Mar 18, 2015 at 10:14 PM, Graham Hay wrote:
> Got there eventually!
>
> $ git verify-pack --verbose bar.pack
> e13e21a1f49704ed35ddc3b15b6111a5f9b34702 commit 220 152 12
> 03691863451ef9db6c69493da1fa556f9338a01d commit 334 227 164
> ... snip ...
> chain length = 50: 2 objects
> bar.pack:
Got there eventually!
$ git verify-pack --verbose bar.pack
e13e21a1f49704ed35ddc3b15b6111a5f9b34702 commit 220 152 12
03691863451ef9db6c69493da1fa556f9338a01d commit 334 227 164
... snip ...
chain length = 50: 2 objects
bar.pack: ok
Now what do I do with it :)
On 18 March 2015 at 13:33, Duy Nguy
On Wed, Mar 18, 2015 at 8:16 PM, Graham Hay wrote:
> I created a repo with over 1GB of images, but it works as expected
> (only pushed 3 objects).
>
> Sorry, I must have done something wrong. I put that script in
> ~/Applications, and checked it worked. Then I ran this:
>
> $ GIT_TRACE=2 PATH=~/Ap
I created a repo with over 1GB of images, but it works as expected
(only pushed 3 objects).
Sorry, I must have done something wrong. I put that script in
~/Applications, and checked it worked. Then I ran this:
$ GIT_TRACE=2 PATH=~/Applications:$PATH git push --set-upstream origin git-wtf
12:48:28
On Wed, Mar 18, 2015 at 7:26 PM, Duy Nguyen wrote:
> It's quite a lot of work :) I created this script named "git" and put
> it in $PATH to capture input for pack-objects. You'll need to update
> "/path/to/real/git" to point to the real binary then you'll get
> /tmp/stdin
Forgot one important sen
On Wed, Mar 18, 2015 at 7:03 PM, Graham Hay wrote:
> Are there any commands that I can use to show exactly what it is trying to
> push?
It's a bit more than a command. If you push when GIT_TRACE is set to
2, you'll see it executes "git pack-objects" command with all its
arguments. This command e
Are there any commands that I can use to show exactly what it is trying to push?
I'll see if I can create a (public) repo that has the same problem.
Thanks for your help.
> This 10804 looks wrong (i.e. sending that many compressed objects).
> Also "80 MiB" sent at that point. If you modify just
On Wed, Mar 18, 2015 at 6:26 PM, Graham Hay wrote:
>> It would help if you pasted the push output. For example, does it stop
>> at 20% at the "compressing objects" line or "writing objects". How
>> many total objects does it say?
>
> It rattles through "compressing objects", and the first 20% of
>
> It would help if you pasted the push output. For example, does it stop
> at 20% at the "compressing objects" line or "writing objects". How
> many total objects does it say?
It rattles through "compressing objects", and the first 20% of
"writing objects", then slows to a crawl.
Writing obje
On Wed, Mar 18, 2015 at 5:55 PM, Graham Hay wrote:
> We have a fairly large repo (~2.4GB), mainly due to binary resources
> (for an ios app). I know this can generally be a problem, but I have a
> specific question.
>
> If I cut a branch, and edit a few (non-binary) files, and push, what
> should
We have a fairly large repo (~2.4GB), mainly due to binary resources
(for an ios app). I know this can generally be a problem, but I have a
specific question.
If I cut a branch, and edit a few (non-binary) files, and push, what
should be uploaded? I assumed it was just the diff (I know whole
compr
17 matches
Mail list logo
