{"thread":{"id":"573","subject":"[ANNOUNCE] No more git-jc tree at cox.net","startedAt":"2005-05-11T19:12:15Z","lastAt":"2005-05-11T19:12:15Z","messageCount":1,"participants":["Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"3056","messageId":"7vbr7hshkg.fsf@assigned-by-dhcp.cox.net","threadId":"573","inReplyTo":null,"subject":"[ANNOUNCE] No more git-jc tree at cox.net","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2005-05-11T19:12:15Z","receivedAt":"2005-05-11T19:12:15Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"As some of you may already know, for the past couple of weeks\nI've been keeping changes to the core GIT that came from\ndiscussion and review on the mailing list in git-jc tree.  The\nintent was to keep the things organized to save time for Linus\nwhen he wants to integrate those good bits.\n\nThe purpose Petr stated for git-pb tree is a superset of the\npurpose of git-jc tree, and currently git-pb tree is fully\nsynched up with git-jc.  I do not see much point in duplicated\neffort, and also git-jc tree housed at my ISP webspace is\nnearing the disc quota.  So I'm removing git-jc tree from there,\nat least until I find it a new home.\n\nJIT (my own Porcelain layer) will still be at the same address,\n<http://members.cox.net/junkio/jit.git/>.\n\nThanks.\n\n"}]}