Git Gone down the drain

[The_Game_Master]

I don't know if anybody noticed but in the past 2 weeks or more the Git Network it stopped updating.

I'm refering to this link http://github.com/mangos/mangos/network so don't imagine anything else.

I was expecting more then 6 months until Git craps his pants and start overloading (remember SVN a while ago?), but looks i was mistaking.

Anybody got any ideea what may have caused the event? There's no data about it anywhere.

[Wyk3d]

Git is working fine. Whether or not a certain service provided by GitHub is working is usually unrelated to that fact.

[The_Game_Master]

If you're working on the master branch then yes, git is working fine. But if you need to apply a dosen of other patches, then no, git is not working fine.

[Wyk3d]

But if you need to apply a dosen of other patches, then no, git is not working fine.

It still works fine even then, assuming you do it properly, by merging branches or at least using properly formatted patches (that you can use with git am) and fixing conflicts is easy if you use the tools which suit you best.

[DasBlub]

If you're working on the master branch then yes, git is working fine. But if you need to apply a dosen of other patches, then no, git is not working fine.

i'm working with ca. 8 branches and i have no problem. this network graphic is nice but it is not needed for the work with git.

[VladimirMangos]

Only can add to prev. post: this is not first time when Network graph service updated with time lags. I remember that this happence from time to time starting from first days when i look at its. Nothing really important affected by this...

[raczman]

This thread just proves that majority of people who criticise git don't understand it, or DVCS in general. Git is working fine, and it handles much bigger projects (linux kernel, anyone?).

[LickedLurk]

I had no problems with GIT, you can ever rescue some things when you do a mistake or something..

merging branches or implement patches works fine aswell...

i mean git is the best thing which could ever happend...

learn the commands and learn to work with it and you will love it...

[SharkPD]

I don't know if anybody noticed but in the past 2 weeks or more the Git Network it stopped updating.

I'm refering to this link http://github.com/mangos/mangos/network so don't imagine anything else.

I was expecting more then 6 months until Git craps his pants and start overloading (remember SVN a while ago?), but looks i was mistaking.

Anybody got any ideea what may have caused the event? There's no data about it anywhere.

Can confirm, always i take a look on it, it stay at date: 15.05.09 what happened with github?

I look there often, to see new Updates or core modifications - anytime for c++ codes too...so please fix the problem with git:(

[freghar]

Perhaps if there weren't too many useless forks (I guess 90% of them haven't received any new objects which aren't on mangos), it would make the graph update faster ..

[The_Game_Master]

This thread just proves that majority of people who criticise git don't understand it, or DVCS in general. Git is working fine, and it handles much bigger projects (linux kernel, anyone?).

Never said that we don't understand git so we criticise it. Like i don't have to be a fan of it or agains it to discuss a problem that occured.

Perhaps if there weren't too many useless forks (I guess 90% of them haven't received any new objects which aren't on mangos), it would make the graph update faster ..

This is very mutch true. Perhaps aproved branches?

[freghar]

This is very mutch true. Perhaps aproved branches?

What do you mean? My point was that many people just click the "fork" button and doesn't care anymore. So they create a new useless fork.

[cyrex]

This thread just proves that majority of people who criticise git don't understand it, or DVCS in general. Git is working fine, and it handles much bigger projects (linux kernel, anyone?).

+1..nevermind, +million

[Patman128]

so please fix the problem with git:(

They don't own or operate GitHub, so it's not their problem. I suppose it's a nice feature, but it would be nice if people stopped forking branches and then forgetting about them.