{"thread":{"id":"28076","subject":"Linux Kernel + GIT SCM","startedAt":"2011-08-12T13:27:30Z","lastAt":"2011-08-13T00:01:21Z","messageCount":2,"participants":["Vecu BOSSEUR","Jakub Narebski"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"173398","messageId":"CACivvv1-UcZdOx+ThLuUkqwL=oy7aETckV+18Fpj_zoXkcXJWQ@mail.gmail.com","threadId":"28076","inReplyTo":null,"subject":"Linux Kernel + GIT SCM","fromName":"Vecu BOSSEUR","fromEmail":"vecu.bosseur@gmail.com","sentAt":"2011-08-12T13:27:30Z","receivedAt":"2011-08-12T13:27:30Z","isPatch":false,"sender":{"key":"vecu.bosseur@gmail.com","avatar":null},"body":"Hello,\n\nI need GIT SCM to allow me to suspend an operation and to resume it\nlater : initial cloning, synchronizing repositories, ...\n\nI believed this was the purpose of the \"GIT Sequencer\" feature\ndevelopped at 2011 Google Summmer Of Code ; please, tell me if I\nmissed something.\n\nAnd I would like to know whether \"kernel.org\" servers will support\nthis feature soon or not.\n\nAnswers much appreciated.\n\nSincerely,\nValentin QUEQUET\n( vecu.bosseur@gmail.com )\n"},{"id":"173437","messageId":"m3pqka18ow.fsf@localhost.localdomain","threadId":"28076","inReplyTo":"CACivvv1-UcZdOx+ThLuUkqwL=oy7aETckV+18Fpj_zoXkcXJWQ@mail.gmail.com","subject":"Re: Linux Kernel + GIT SCM","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2011-08-13T00:01:21Z","receivedAt":"2011-08-13T00:01:21Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"Vecu BOSSEUR <vecu.bosseur@gmail.com> writes:\n\n> Hello,\n> \n> I need GIT SCM to allow me to suspend an operation and to resume it\n> later : initial cloning, synchronizing repositories, ...\n> \n> I believed this was the purpose of the \"GIT Sequencer\" feature\n> developped at 2011 Google Summmer Of Code ; please, tell me if I\n> missed something.\n> \n> And I would like to know whether \"kernel.org\" servers will support\n> this feature soon or not.\n\nNo, \"Git sequencer\" has nothing to do with resumable (and suspendable)\nclone, fetch or push.  Resumable transport is not implemented, and it\nlooks like ti would be difficult to add.\n\nThe sequencer project is about engine that it is to be used by rebase,\nmultiple cherry-pick, multiple revert, and git-am.  Among others it is\nmeant to increase consistency between those commands.\n \n-- \nJakub Narębski\n"}]}