Re: Problem while cloning a git repo

2013-11-17 Thread ycollette . nospam
When I clone a git repo from github (via https), I've no problems. It looks like that the problem is only related to my special repo with big zip commited inside. YC - Mail original - De: Yann COLLETTE ycollette.nos...@free.fr À: git@vger.kernel.org Envoyé: Jeudi 14 Novembre 2013

Re: Add a bugzilla website

2013-11-17 Thread ycollette . nospam
people here are very reluctant to use a bugtracking tool ... YC - Mail original - De: brian m. carlson sand...@crustytoothpaste.net À: ycollette nospam ycollette.nos...@free.fr Cc: git@vger.kernel.org Envoyé: Vendredi 15 Novembre 2013 23:57:09 Objet: Re: Add a bugzilla website On Fri

Re: Add a bugzilla website

2013-11-15 Thread ycollette . nospam
And the conclusion is ? No bugzilla tool installed because somebody want to build a gitbased bugzilla thing ? YC - Mail original - De: Damien Wyart damien.wy...@gmail.com À: ycollette nospam ycollette.nos...@free.fr Cc: git@vger.kernel.org Envoyé: Vendredi 15 Novembre 2013 09:53:26

Re: Add a bugzilla website

2013-11-15 Thread ycollette . nospam
the bugs are tracked, you can see if a bug has been already filled and put some additional informations if necessary. I will have a look at the JIRA thing. YC - Mail original - De: Konstantin Khomoutov flatw...@users.sourceforge.net À: ycollette nospam ycollette.nos...@free.fr Cc: git

Add a bugzilla website

2013-11-14 Thread ycollette . nospam
Hello, I just wanted to ask a question: why is there no bugzilla website for git ? It's better to put bugs into such a tool to follow there evolution than to manage bugs via a developpment mailing list ... Best regards, YC -- To unsubscribe from this list: send the line unsubscribe git in the

Problem while cloning a git repo

2013-11-12 Thread ycollette . nospam
Hello, When I clone a repository, I get an error from git: git clone http://192.168.0.18:8080/test test_Gerrit Clonage dans 'test_Gerrit'... remote: Counting objects: 25106, done remote: Finding sources: 100% (25106/25106) error: RPC failed; result=56, HTTP code = 200iB | 8.12 MiB/s fatal: