Re: Problem while cloning a git repo
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 09:20:51 Objet: Re: Problem while cloning a git repo I am not able to clone via https because gerrit doesn't propose this way of cloning. When I clone via http, I see that git is starting the download of objects: remote: Counting objects: 256, done remote: Finding sources: 100% (256/256) Receiving objects: 46% ... (this part always fails at 46 %). So, I think that the proxy part is not a problem (there is no proxy set here). If I set GIT_CURL_VERBOSE=1 before cloning, I've got the following error: * Problem (2) in the Chunked-Encoded data * Closing connection 1 YC Le 14/11/2013 00:40, brian m. carlson a écrit : On Wed, Nov 13, 2013 at 08:43:28AM +0100, Yann COLLETTE wrote: Hello, When I perform the git clone via git, it works. The problem is only happening via http. I tried to play with http.postBuffer and I set this parameter to it's maximum (a little bit before a git clone triggered a memory alloc problem) and I see that something big is trying to be downloaded. But I don't see such a big file in my history of commits. The maximum one seems to be around 50 Mo ... Please keep the list in CC. http.postBuffer doesn't affect clones, only pushes, so that isn't relevant here. You're experiencing something that is dropping the connection over HTTP. So you either have a bad proxy, or something else is causing the connection to be dropped. Since it's only over HTTP, I suspect it's the former. Do you have HTTPS, and if so, does it work if you try to clone over that? -- To unsubscribe from this list: send the line unsubscribe git in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line unsubscribe git in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Add a bugzilla website
On most linux distro bugzilla website, there are some people dedicated to triaging bugs (finding duplicated bugs, asking for more informations, closing old and / or resolved bugs). To have an efficient bugtracking tool needs to have some people dedicated to this. But for the user, it's a better approach. For example, I do not need to register to the devel list and I do not have to watch all mails to locate the one which concerns my bug. It works nicely with fedora, magieia and other distro / tools, so I don't know why this shouldn't work fine with git ? But as far as I can read, most 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, Nov 15, 2013 at 10:40:47AM +0100, ycollette.nos...@free.fr wrote: And the conclusion is ? No bugzilla tool installed because somebody want to build a gitbased bugzilla thing ? Personally, I do not want Yet Another Bugzilla Account. A project is significantly less likely to get a patch from me if I have to create an account to report a bug. Most of the patches I send to various projects are for bugs I've experienced and want to provide a fix for, so I send a small number of patches to many projects. I feel that the mailing list workflow ends up working very well for Git and it provides a low barrier to entry for those that want to send just one or two patches for problems that they're experiencing. It also allows me to see and comment on virtually every patch on the list, while ignoring threads I am not interested in, a combination which is difficult to achieve with a web-based bug tracker. -- brian m. carlson / brian with sandals: Houston, Texas, US +1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187 -- To unsubscribe from this list: send the line unsubscribe git in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Add a bugzilla website
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 Objet: Re: Add a bugzilla website * ycollette.nos...@free.fr ycollette.nos...@free.fr [2013-11-15 08:44]: 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 ... http://thread.gmane.org/gmane.comp.version-control.git/191835/focus=192464 -- Damien Wyart -- To unsubscribe from this list: send the line unsubscribe git in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Add a bugzilla website
OK, thanks for these informations. From a user perspective, having this volume of devel mails flooding all the bugs mail is very annoying. And following the status of a bug and the history of this bug is very hard too. The bugzilla approach is really useful for the user who is reporting bugs: all 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@vger.kernel.org Envoyé: Vendredi 15 Novembre 2013 10:51:32 Objet: Re: Add a bugzilla website On Fri, 15 Nov 2013 10:40:47 +0100 (CET) ycollette.nos...@free.fr wrote: And the conclusion is ? No bugzilla tool installed because somebody want to build a gitbased bugzilla thing ? Well, no, the real answer is that for those who actually write code and apply patches, an e-mail based workflow is simpler: Git has tools to apply patches right from Unix mailboxes, so one is able to just save a thread with the final patch series to a file and apply it. Some people also prefer discussing patches inline -- in the same e-mail thread the patch series being discussed had started. I'm aware of at least one big project sporting the same approach to handling bugs -- PostgreSQL. But there was an announcement that an experimental JIRA instance has been set up for Git [1]. I'm not sure what its current status is, but you could look at it. Also Git's mirror on github [2] supposedly provides for pull requests. Again, not sure whether/how they're handled. 1. http://git-blame.blogspot.ru/2012/02/experimental-git-bug-tracker.html 2. https://github.com/git/git/ -- To unsubscribe from this list: send the line unsubscribe git in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Add a bugzilla website
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 body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Problem while cloning a git repo
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: The remote end hung up unexpectedly fatal: early EOF fatal: index-pack failed The repo has some big zip files commited inside. I use fedora 19 64 bits and git version is 1.8.3.1. Best regards, YC -- To unsubscribe from this list: send the line unsubscribe git in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
