Comments on: let’s move that source code so it doesn’t get lazy http://blog.lydiapintscher.de/2010/06/19/lets-move-that-source-code-so-it-doesnt-get-lazy/ everything that comes into my mind Wed, 08 Feb 2012 13:21:43 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Jeff Mitchell http://blog.lydiapintscher.de/2010/06/19/lets-move-that-source-code-so-it-doesnt-get-lazy/comment-page-1/#comment-254070 Jeff Mitchell Wed, 30 Jun 2010 18:20:30 +0000 http://blog.lydiapintscher.de/?p=656#comment-254070 @Habarnam Indeed there is. However, note that the HTTP method is *very slow*, and doesn't give you status updates in the middle...so it can appear to "hang" while you do commands. The initial clone especially can take a beastly amount of time -- maybe 10 minutes or more. You can try setting the GIT_CURL_VERBOSE environment variable to 1 to get quite verbose status messages. If you do this you may notice that you get a ton of 404 errors; I don't know the details of how Git works over HTTP but it seems to request a lot of objects that are in packs before requesting the pack itself. This is probably one reason why it's sooooo slooooooow. But, ignore those errors and eventually it'll complete. One last thing -- when using the http method, be sure to specify the .git at the end: git clone http://git.kde.org/amarok/amarok.git Good luck! @Habarnam

Indeed there is. However, note that the HTTP method is *very slow*, and doesn’t give you status updates in the middle…so it can appear to “hang” while you do commands. The initial clone especially can take a beastly amount of time — maybe 10 minutes or more. You can try setting the GIT_CURL_VERBOSE environment variable to 1 to get quite verbose status messages.

If you do this you may notice that you get a ton of 404 errors; I don’t know the details of how Git works over HTTP but it seems to request a lot of objects that are in packs before requesting the pack itself. This is probably one reason why it’s sooooo slooooooow. But, ignore those errors and eventually it’ll complete.

One last thing — when using the http method, be sure to specify the .git at the end:

git clone http://git.kde.org/amarok/amarok.git

Good luck!

]]> By: habarnam http://blog.lydiapintscher.de/2010/06/19/lets-move-that-source-code-so-it-doesnt-get-lazy/comment-page-1/#comment-254069 habarnam Wed, 30 Jun 2010 11:10:25 +0000 http://blog.lydiapintscher.de/?p=656#comment-254069 Hello Lidya, Is there a http:// access method for the git repository (I haven't managed to find mentions of one so far)? Due to some company firewall policies I can't access the git:// repositories and I can't get my daily fix of Amarok. Hello Lidya,

Is there a http:// access method for the git repository (I haven’t managed to find mentions of one so far)?

Due to some company firewall policies I can’t access the git:// repositories and I can’t get my daily fix of Amarok.

]]> By: Looking at Konversation « Bobulate http://blog.lydiapintscher.de/2010/06/19/lets-move-that-source-code-so-it-doesnt-get-lazy/comment-page-1/#comment-254058 Looking at Konversation « Bobulate Tue, 22 Jun 2010 17:23:51 +0000 http://blog.lydiapintscher.de/?p=656#comment-254058 [...] course, since it’s in git (on git.kde.org now!) I may as well see if I can write some patches for these issues, if only as practice in using [...] [...] course, since it’s in git (on git.kde.org now!) I may as well see if I can write some patches for these issues, if only as practice in using [...]

]]> By: Ulrik Mikaelsson http://blog.lydiapintscher.de/2010/06/19/lets-move-that-source-code-so-it-doesnt-get-lazy/comment-page-1/#comment-254052 Ulrik Mikaelsson Mon, 21 Jun 2010 18:21:02 +0000 http://blog.lydiapintscher.de/?p=656#comment-254052 Great to hear the Git-transitions will finally likely happen. Being a drive-by-commiter for a few years back, and for a time tried to maintain my own experimental patchset-branch of KDE over a few releases, I've found SVN more than a little unwieldy. Sure, I've managed decently with git-svn, but great news to hear KDE will now support distributed development models. When time allows, I feel inspired to restart my little "Hotkeys-mode" branch of KDE. :) Great to hear the Git-transitions will finally likely happen.

Being a drive-by-commiter for a few years back, and for a time tried to maintain my own experimental patchset-branch of KDE over a few releases, I’ve found SVN more than a little unwieldy.

Sure, I’ve managed decently with git-svn, but great news to hear KDE will now support distributed development models. When time allows, I feel inspired to restart my little “Hotkeys-mode” branch of KDE. :)

]]> By: Jeff Mitchell http://blog.lydiapintscher.de/2010/06/19/lets-move-that-source-code-so-it-doesnt-get-lazy/comment-page-1/#comment-254049 Jeff Mitchell Mon, 21 Jun 2010 15:09:16 +0000 http://blog.lydiapintscher.de/?p=656#comment-254049 Two cells to the right, in the Notes entry for that line. Two cells to the right, in the Notes entry for that line.

]]> By: Rick Stanley http://blog.lydiapintscher.de/2010/06/19/lets-move-that-source-code-so-it-doesnt-get-lazy/comment-page-1/#comment-254048 Rick Stanley Mon, 21 Jun 2010 15:00:22 +0000 http://blog.lydiapintscher.de/?p=656#comment-254048 @Lydia In the Spreadsheet, in Cell D3, it says: <blockquote>"Ruby on Rails. JavaScript ActiveMQ/STOMP. Sphinx. Custom git-daemon. MySQL. *SEE WARNING*"</blockquote> Where is the **WARNING**? Am I missing something? @Lydia

In the Spreadsheet, in Cell D3, it says:

“Ruby on Rails. JavaScript ActiveMQ/STOMP. Sphinx. Custom git-daemon. MySQL. *SEE WARNING*”

Where is the **WARNING**? Am I missing something?

]]> By: Lydia http://blog.lydiapintscher.de/2010/06/19/lets-move-that-source-code-so-it-doesnt-get-lazy/comment-page-1/#comment-254040 Lydia Mon, 21 Jun 2010 09:55:17 +0000 http://blog.lydiapintscher.de/?p=656#comment-254040 Woah.... I have fans!!!1111eleven :D But you're right. I'll try to make it more readable when I have a few mins for it. Woah…. I have fans!!!1111eleven :D
But you’re right. I’ll try to make it more readable when I have a few mins for it.

]]> By: areader http://blog.lydiapintscher.de/2010/06/19/lets-move-that-source-code-so-it-doesnt-get-lazy/comment-page-1/#comment-254035 areader Sun, 20 Jun 2010 16:17:51 +0000 http://blog.lydiapintscher.de/?p=656#comment-254035 Please use readable fonts. Gray type on a white background is difficult to read. thx, a fan Please use readable fonts. Gray type on a white background is difficult to read.

thx, a fan

]]> By: Jeff Mitchell http://blog.lydiapintscher.de/2010/06/19/lets-move-that-source-code-so-it-doesnt-get-lazy/comment-page-1/#comment-254031 Jeff Mitchell Sat, 19 Jun 2010 16:16:56 +0000 http://blog.lydiapintscher.de/?p=656#comment-254031 @friesoft If you're a kde developer, cloning will be quite easy -- a simple command passed in to ssh via git.kde.org. It's worth noting that even if we had gone with self-hosted Gitorious, we would not have been prepared (at least not currently, and not in the foreseeable future) to offer the ability for the public to create clones. Our capacity is much more limited than Gitorious.org. Although Tom seems to feel like this is due to NIN (although I don't know what Trent Reznor has to do with KDE, but if there's even a tenuous connection, awesome!), the plain fact is that we were unable to reach agreements with the Gitorious.org folks for hosting there. Once Gitorious.org was off the table, the focus switched to whether, in a *self-hosted* scenario, Gitorious was still our best option. As the report concludes, it wasn't. (Also, using existing bits of software, like Gitolite, Redmine, and cgit, is hardly NIH syndrome at work.) @friesoft If you’re a kde developer, cloning will be quite easy — a simple command passed in to ssh via git.kde.org.

It’s worth noting that even if we had gone with self-hosted Gitorious, we would not have been prepared (at least not currently, and not in the foreseeable future) to offer the ability for the public to create clones. Our capacity is much more limited than Gitorious.org.

Although Tom seems to feel like this is due to NIN (although I don’t know what Trent Reznor has to do with KDE, but if there’s even a tenuous connection, awesome!), the plain fact is that we were unable to reach agreements with the Gitorious.org folks for hosting there. Once Gitorious.org was off the table, the focus switched to whether, in a *self-hosted* scenario, Gitorious was still our best option. As the report concludes, it wasn’t. (Also, using existing bits of software, like Gitolite, Redmine, and cgit, is hardly NIH syndrome at work.)

]]> By: Eike Hein http://blog.lydiapintscher.de/2010/06/19/lets-move-that-source-code-so-it-doesnt-get-lazy/comment-page-1/#comment-254030 Eike Hein Sat, 19 Jun 2010 15:17:58 +0000 http://blog.lydiapintscher.de/?p=656#comment-254030 I won't rule it out, but I also can't make any promises - it's a question of capacity (both technical and manpower), liability and so on. Right now the most important part is to get the ball rolling again and make forward progress on the SVN->Git migration of KDE (let's keep in mind that while a small number of projects got to test Gitorious.org, most of KDE's devs are still stuck with SVN!) after being blocked for eight months or so on the negotiations with Shortcut. So we're looking to ramp things up quickly, and then we'll see in the future in what ways we can extend our offering further :). I won’t rule it out, but I also can’t make any promises – it’s a question of capacity (both technical and manpower), liability and so on. Right now the most important part is to get the ball rolling again and make forward progress on the SVN->Git migration of KDE (let’s keep in mind that while a small number of projects got to test Gitorious.org, most of KDE’s devs are still stuck with SVN!) after being blocked for eight months or so on the negotiations with Shortcut. So we’re looking to ramp things up quickly, and then we’ll see in the future in what ways we can extend our offering further :) .

]]>