Hi all,
recently I got a:
remote: fatal: *object 534a44ef7703fdfe13e609b3e87e98bd52af60f8 is corrupted
*
error: git upload-pack: git-pack-objects died with error.
fatal: git upload-pack: aborting due to possible repository corruption on
the remote side.
remote: aborting due to possible repository
Thanks, Inigo. I guess the real question I have is less about ways to
prevent this from happening, and more about what to do if it DOES happen.
Prevention is great, and this is the first time something like this has
happened to us. But it brought into focus just how easy it actually is for
someone
On Wed, 21 Nov 2012, Brian Kotek wrote:
One of the developers (new to Git) did something bizarre like merge an old
branch into a new one and then push it. As a result, a lot of files were
deleted or changed (back to older versions). No one initially noticed (we
have a CI server but it only runs
I've been using Git for a while and I'm fairly well-versed with it.
However, an issue came up at work yesterday that was a bear to resolve. I'd
like to know if anyone has any advice or if there's a preferred way to deal
with this.
One of the developers (new to Git) did something bizarre like me
I'm working on converting 20 cvs modules into snv/git repositories in order
to determine which is most appropriate for my client's needs.
The module to repo conversion is going well because the cvs2svn/git tools
work as documented. Thanks for that.
I've been able to write some autobranch code t
On Wednesday, November 21, 2012 4:49:43 PM UTC+1, kumar wrote:
> hi
>
> in windows using git GUI when i tried to do git add for 200,000 files
> (18GB) it took about 5hr is that normal after which i got the below error?
>
> Updating the Git index failed. A rescan will be automatically started to
hi
in windows using git GUI when i tried to do git add for 200,000 files
(18GB) it took about 5hr is that normal after which i got the below error?
Updating the Git index failed. A rescan will be automatically started to
resynchronize git-gui.
with lots of this warning
warning: LF will be repla
On Wednesday, November 21, 2012 3:08:19 PM UTC+1, John McKown wrote:
> I was thinking that the OP was saying that the three operations together
> were taking a long time. I guess it would be helpful to know which of the
> commands is taking so long, the "add", "commit", or the "push". If it is
I was thinking that the OP was saying that the three operations together
were taking a long time. I guess it would be helpful to know which of the
commands is taking so long, the "add", "commit", or the "push". If it is
the "add", I don't know a way to speed it up. That is all done locally. The
On Wednesday, November 21, 2012 10:58:24 AM UTC+1, kumar wrote:
> Hi
>
> I am setting up a repository for the first. I already have a project of
> 18GB about 200,000 files.
> Currently these are the steps i am doing
>
> git add .
> git commit -m "Initial"
> git push
>
> Considering the size and
Hi
I am setting up a repository for the first. I already have a project of
18GB about 200,000 files.
Currently these are the steps i am doing
git add .
git commit -m "Initial"
git push
Considering the size and 3 steps it is taking time. Is there an faster way
to accomplish this? Is it possib
11 matches
Mail list logo
