{"thread":{"id":"8731","subject":"Problem with Linus's git repository?","startedAt":"2007-06-26T14:45:23Z","lastAt":"2007-06-29T13:00:09Z","messageCount":10,"participants":["walt","Linus Torvalds","Junio C Hamano","Johannes Schindelin","Andreas Ericsson"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"45836","messageId":"f5r8q5$pbr$1@sea.gmane.org","threadId":"8731","inReplyTo":null,"subject":"Problem with Linus's git repository?","fromName":"walt","fromEmail":"wa1ter@myrealbox.com","sentAt":"2007-06-26T14:45:23Z","receivedAt":"2007-06-26T14:45:23Z","isPatch":false,"sender":{"key":"wa1ter@myrealbox.com","avatar":null},"body":"For two days I've been unable to pull from Linus's kernel\ngit repository.  The reason seems to be that HEAD is a\nsymlink to refs/heads/master, which appears to be missing.\n\nI'm wondering if Linus's personal version of git is broken ;o)\n"},{"id":"45837","messageId":"alpine.LFD.0.98.0706260935440.8675@woody.linux-foundation.org","threadId":"8731","inReplyTo":"f5r8q5$pbr$1@sea.gmane.org","subject":"Re: Problem with Linus's git repository?","fromName":"Linus Torvalds","fromEmail":"torvalds@linux-foundation.org","sentAt":"2007-06-26T16:43:37Z","receivedAt":"2007-06-26T16:43:37Z","isPatch":false,"sender":{"key":"torvalds@linux-foundation.org","avatar":"https://avatars.githubusercontent.com/u/1024025?v=4"},"body":"\n\nOn Tue, 26 Jun 2007, walt wrote:\n>\n> For two days I've been unable to pull from Linus's kernel\n> git repository.  The reason seems to be that HEAD is a\n> symlink to refs/heads/master, which appears to be missing.\n\nIt's not missing, it's packed. I tend to re-pack after I make a release, \nand this time I did it after -rc6.\n\nI assume you're using http, and probably not a very recent version.\n\n> I'm wondering if Linus's personal version of git is broken ;o)\n\nhttp fetching has always been the ugly step-child of the other protocols. \nI personally dislike it a lot. But it _should_ work even with packed refs, \nat least if recent enough.\n\nI just tested, it seems to work for me (I didn't wait for the clone to \nsucceed, but it certainly got started).\n\n\t\tLinus\n"},{"id":"45916","messageId":"Pine.LNX.4.64.0706270636140.7038@x2.ybpnyarg","threadId":"8731","inReplyTo":"alpine.LFD.0.98.0706260935440.8675@woody.linux-foundation.org","subject":"Re: Problem with Linus's git repository?","fromName":"walt","fromEmail":"wa1ter@myrealbox.com","sentAt":"2007-06-27T13:41:48Z","receivedAt":"2007-06-27T13:41:48Z","isPatch":false,"sender":{"key":"wa1ter@myrealbox.com","avatar":null},"body":"\n\nOn Tue, 26 Jun 2007, Linus Torvalds wrote:\n\n>\n>\n> On Tue, 26 Jun 2007, walt wrote:\n> >\n> > For two days I've been unable to pull from Linus's kernel\n> > git repository.  The reason seems to be that HEAD is a\n> > symlink to refs/heads/master, which appears to be missing.\n>\n> It's not missing, it's packed. I tend to re-pack after I make a release,\n> and this time I did it after -rc6...\n\nSometime overnight this problem disappeared.  I haven't actually\ntested this idea, but I have a hunch that your commit yesterday\nof \"Fix zero-object version-2 packs\" is the reason.\n\nIf the problem recurs I'll follow up on it.\n\nThanks.\n"},{"id":"45928","messageId":"alpine.LFD.0.98.0706270932040.8675@woody.linux-foundation.org","threadId":"8731","inReplyTo":"Pine.LNX.4.64.0706270636140.7038@x2.ybpnyarg","subject":"Re: Problem with Linus's git repository?","fromName":"Linus Torvalds","fromEmail":"torvalds@linux-foundation.org","sentAt":"2007-06-27T16:34:09Z","receivedAt":"2007-06-27T16:34:09Z","isPatch":false,"sender":{"key":"torvalds@linux-foundation.org","avatar":"https://avatars.githubusercontent.com/u/1024025?v=4"},"body":"\n\nOn Wed, 27 Jun 2007, walt wrote:\n> >\n> > It's not missing, it's packed. I tend to re-pack after I make a release,\n> > and this time I did it after -rc6...\n> \n> Sometime overnight this problem disappeared.  I haven't actually\n> tested this idea, but I have a hunch that your commit yesterday\n> of \"Fix zero-object version-2 packs\" is the reason.\n\nNo, I think the reason is simply that I pushed more updates to kernel.org, \nso now the kernel git repo has an explicit and separate \"master\" branch \nagain.\n\nWhat is your git version? The _real_ fix probably is to just upgrade. Are \nyou using that broken(*) Debian git package by any chance?\n\n\t\tLinus\n\n(*) By broken I mean \"stable cannot be bothered to upgrade packages to \nmodern versions, and is still on some ancient 1.4-based git version\"\n"},{"id":"45949","messageId":"7v6458pv6n.fsf@assigned-by-dhcp.pobox.com","threadId":"8731","inReplyTo":"alpine.LFD.0.98.0706270932040.8675@woody.linux-foundation.org","subject":"Re: Problem with Linus's git repository?","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2007-06-28T04:19:44Z","receivedAt":"2007-06-28T04:19:44Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Linus Torvalds <torvalds@linux-foundation.org> writes:\n\n> What is your git version? The _real_ fix probably is to just upgrade. Are \n> you using that broken(*) Debian git package by any chance?\n>\n> \t\tLinus\n>\n> (*) By broken I mean \"stable cannot be bothered to upgrade packages to \n> modern versions, and is still on some ancient 1.4-based git version\"\n\nWell, although git 1.4 is ancient in git timescale, you can keep\nyour repository friendly with older versions of git and 1.4\ncertainly is not too old for that.  In other words, newer git\nlets you choose to make your repository unreadable by 1.4, and\nyou chose to do so, perhaps for a good reason.\n\nShould we call git 1.5 \"backward incompatible\" with 1.4, because\nit allows you (or anybody) to make that choice?  I dunno.\n"},{"id":"45984","messageId":"Pine.LNX.4.64.0706280632540.5321@x2.ybpnyarg","threadId":"8731","inReplyTo":"alpine.LFD.0.98.0706270932040.8675@woody.linux-foundation.org","subject":"Re: Problem with Linus's git repository?","fromName":"walt","fromEmail":"wa1ter@myrealbox.com","sentAt":"2007-06-28T13:37:49Z","receivedAt":"2007-06-28T13:37:49Z","isPatch":false,"sender":{"key":"wa1ter@myrealbox.com","avatar":null},"body":"\n\nOn Wed, 27 Jun 2007, Linus Torvalds wrote:\n\n>\n>\n> On Wed, 27 Jun 2007, walt wrote:\n> > >\n> > > It's not missing, it's packed. I tend to re-pack after I make a release,\n> > > and this time I did it after -rc6...\n> >\n> > Sometime overnight this problem disappeared.  I haven't actually\n> > tested this idea, but I have a hunch that your commit yesterday\n> > of \"Fix zero-object version-2 packs\" is the reason.\n>\n> No, I think the reason is simply that I pushed more updates to kernel.org,\n> so now the kernel git repo has an explicit and separate \"master\" branch\n> again.\n>\n> What is your git version? The _real_ fix probably is to just upgrade. Are\n> you using that broken(*) Debian git package by any chance?\n\nNo, every morning I pull from you and Junio and Petr Baudis using cg-update,\nso I'm very much current.  I notice that cg-update specifically does an\nhttp GET on kernel/git/torvalds/linux-2.6.git/HEAD which is actually a\nsymlink to your refs/heads/master.  Your 'master' now exists, but didn't\nexist two days ago as far I could see from my end.\n\nThe kernel.org server returned a 'you don't have permission to read\nkernel/git/torvalds/linux-2.6.git/HEAD on this server', not a 404.\nI tried two different ftp clients which also could not see your\n'master' file until yesterday.\n\nI notice that Petr hasn't made any changes to cogito for a long\ntime, so maybe it needs some updating?  Dunno.\n\n\n\n--- Scanned by M+ Guardian Messaging Firewall ---\n"},{"id":"45986","messageId":"Pine.LNX.4.64.0706281620240.4438@racer.site","threadId":"8731","inReplyTo":"Pine.LNX.4.64.0706280632540.5321@x2.ybpnyarg","subject":"Re: Problem with Linus's git repository?","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2007-06-28T15:20:54Z","receivedAt":"2007-06-28T15:20:54Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Thu, 28 Jun 2007, walt wrote:\n\n> I notice that Petr hasn't made any changes to cogito for a long time, so \n> maybe it needs some updating?  Dunno.\n\nPasky announced that he will be discontinuing cogito.\n\nHth,\nDscho\n"},{"id":"45987","messageId":"alpine.LFD.0.98.0706280840570.8675@woody.linux-foundation.org","threadId":"8731","inReplyTo":"Pine.LNX.4.64.0706280632540.5321@x2.ybpnyarg","subject":"Re: Problem with Linus's git repository?","fromName":"Linus Torvalds","fromEmail":"torvalds@linux-foundation.org","sentAt":"2007-06-28T15:41:33Z","receivedAt":"2007-06-28T15:41:33Z","isPatch":false,"sender":{"key":"torvalds@linux-foundation.org","avatar":"https://avatars.githubusercontent.com/u/1024025?v=4"},"body":"\n\nOn Thu, 28 Jun 2007, walt wrote:\n> \n> No, every morning I pull from you and Junio and Petr Baudis using cg-update,\n> so I'm very much current.  I notice that cg-update specifically does an\n> http GET on kernel/git/torvalds/linux-2.6.git/HEAD which is actually a\n> symlink to your refs/heads/master.  Your 'master' now exists, but didn't\n> exist two days ago as far I could see from my end.\n\nOh, don't use \"cg-update\", or just fix it to do \"git pull\".\n\nThat explains it. cogito simply is not maintained any more.\n\n\t\tLinus\n"},{"id":"46046","messageId":"Pine.LNX.4.64.0706290537130.7055@x2.ybpnyarg","threadId":"8731","inReplyTo":"alpine.LFD.0.98.0706280840570.8675@woody.linux-foundation.org","subject":"Re: Problem with Linus's git repository?","fromName":"walt","fromEmail":"wa1ter@myrealbox.com","sentAt":"2007-06-29T12:47:28Z","receivedAt":"2007-06-29T12:47:28Z","isPatch":false,"sender":{"key":"wa1ter@myrealbox.com","avatar":null},"body":"\n\nOn Thu, 28 Jun 2007, Linus Torvalds wrote:\n\n\n> On Thu, 28 Jun 2007, walt wrote:\n> >\n> > No, every morning I pull from you and Junio and Petr Baudis using cg-update,\n\n\n> Oh, don't use \"cg-update\", or just fix it to do \"git pull\".\n\nI'm happy to stick with using git.  From reading the latest Docs, it seems\nthat git-pull -v will do what I need (I think).\n\nThat's what I did just now to update from you and Junio, and the output\nseemed exactly appropriate -- ended with a fast-forward and no errors\nfor either one.\n\nHowever, a git-fsck turned up four dangling commits for Junio, and 42\ndanglers for you, including a mix of blobs, trees, and commits.\n\nWill a simple git-prune bring me correctly up to date, or am I missing\nsome steps?\n\nThanks!\n\n\n--- Scanned by M+ Guardian Messaging Firewall ---\n"},{"id":"46047","messageId":"46850259.8030708@op5.se","threadId":"8731","inReplyTo":"Pine.LNX.4.64.0706290537130.7055@x2.ybpnyarg","subject":"Re: Problem with Linus's git repository?","fromName":"Andreas Ericsson","fromEmail":"ae@op5.se","sentAt":"2007-06-29T13:00:09Z","receivedAt":"2007-06-29T13:00:09Z","isPatch":false,"sender":{"key":"ae@op5.se","avatar":"https://gravatar.com/avatar/426e89595c75a8f5252dd0c989e5fabe5bcac616e68557427ad9aef6b0ca342a?d=mp&s=160"},"body":"walt wrote:\n> \n> On Thu, 28 Jun 2007, Linus Torvalds wrote:\n> \n>> On Thu, 28 Jun 2007, walt wrote:\n>>> No, every morning I pull from you and Junio and Petr Baudis using cg-update,\n> \n> \n>> Oh, don't use \"cg-update\", or just fix it to do \"git pull\".\n> \n> I'm happy to stick with using git.  From reading the latest Docs, it seems\n> that git-pull -v will do what I need (I think).\n> \n> That's what I did just now to update from you and Junio, and the output\n> seemed exactly appropriate -- ended with a fast-forward and no errors\n> for either one.\n> \n> However, a git-fsck turned up four dangling commits for Junio, and 42\n> danglers for you, including a mix of blobs, trees, and commits.\n> \n\nYou will see dangling commits, blobs and trees from Junio because he rewinds\nhis 'pu' branch.\n\nI'm not sure why you see any from Linus, as I'm not aware of any rewinding\nin the official kernel tree (unless you're talking about some other repo,\nin which case I'm clueless).\n\n> Will a simple git-prune bring me correctly up to date, or am I missing\n> some steps?\n> \n\nYou're already up to date. The dangling commits do not hurt your repo\nin any way. Nor do they hurt the performance of any of the tools you\nnormally use. fsck suffers a bit from them, because it has to care\nabout them, but the normal DAG-traversing tools will never even\nsee them.\n\ngit prune would remove them and save you a tiny bit of diskspace.\nNext time you pull from Junio, you'll most likely get orphaned commits\nagain though, meaning blobs, trees and commits will end up dangling once\nmore. It's perfectly normal and nothing to worry about.\n\nFor repo maintenance, I run \"git gc\" once a month on my local copies.\nMore to let my laptop do something while I'm fiddling with receipts and\nstuff than for any real need (the idea of idle computers offend me for\nsome reason).\n\n-- \nAndreas Ericsson                   andreas.ericsson@op5.se\nOP5 AB                             www.op5.se\nTel: +46 8-230225                  Fax: +46 8-230231\n"}]}