{"thread":{"id":"52016","subject":"Re: RFE: use patchwork to submit a patch","startedAt":"2019-10-10T20:20:53Z","lastAt":"2019-10-10T20:36:18Z","messageCount":3,"participants":["Jonathan Nieder","Eric Wong"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"383834","messageId":"20191010202049.GB191800@google.com","threadId":"52016","inReplyTo":"20191010144150.hqiosvwolm3lmzp5@chatter.i7.local","subject":"Re: RFE: use patchwork to submit a patch","fromName":"Jonathan Nieder","fromEmail":"jrnieder@gmail.com","sentAt":"2019-10-10T20:20:49Z","receivedAt":"2019-10-10T20:20:53Z","isPatch":false,"sender":{"key":"jrnieder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/281595?v=4"},"body":"(+cc: git)\nHi,\n\nKonstantin Ryabitsev wrote[1]:\n\n> How I envision this would work:\n>\n> - user creates an account (which requires a mail confirmation)\n> - they choose a \"submit patch\" option from the menu\n> - the patch submission screen has a succession of screens:\n\nInteresting!  This reminds me a bit of https://gitgitgadget.github.io\n(except using patchwork instead of github pull requests as substrate).\n\nThat leads me to wonder: should these kinds of tools share some code?\nAre there any subtleties that web-to-mail patch submission interfaces\nhave in common or can learn from each other?\n\nThanks,\nJonathan\n\n[1] https://lore.kernel.org/workflows/20191010144150.hqiosvwolm3lmzp5@chatter.i7.local/\n"},{"id":"383835","messageId":"20191010202151.GC191800@google.com","threadId":"52016","inReplyTo":"20191010200528.GA5612@dcvr","subject":"Re: RFE: use patchwork to submit a patch","fromName":"Jonathan Nieder","fromEmail":"jrnieder@gmail.com","sentAt":"2019-10-10T20:21:51Z","receivedAt":"2019-10-10T20:21:56Z","isPatch":false,"sender":{"key":"jrnieder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/281595?v=4"},"body":"Eric Wong wrote:\n> Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:\n\n>> This is actually really fast if you already have a local copy of the\n>> repository with most objects. Try this yourself if you have\n>> torvalds/linux.git locally:\n>>\n>> git clone --bare -s torvalds/linux.git test\n>\n> Yep, -s (--shared) makes cloning really cheap.  One of my goals is to get\n>\n> \tgit clone -s https://example.com/torvalds/linux.git\n>\n> and\n>\n> \tgit clone -s https://example.com/torvalds/linux.git/clone.bundle\n>\n> working.  That would make it easier for new contributors to\n> setup lightweight clones and pull in history on an as-needed\n> basis w/o hacks like shallow cloning.\n\nDoes \"git clone --filter=blob:none\" do what you're looking for?\n\nThanks,\nJonathan\n"},{"id":"383836","messageId":"20191010203617.o6gyhnkjbbd7njnw@dcvr","threadId":"52016","inReplyTo":"20191010202151.GC191800@google.com","subject":"Re: RFE: use patchwork to submit a patch","fromName":"Eric Wong","fromEmail":"e@80x24.org","sentAt":"2019-10-10T20:36:17Z","receivedAt":"2019-10-10T20:36:18Z","isPatch":false,"sender":{"key":"e@80x24.org","avatar":null},"body":"Jonathan Nieder <jrnieder@gmail.com> wrote:\n> Eric Wong wrote:\n> > Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:\n> \n> >> This is actually really fast if you already have a local copy of the\n> >> repository with most objects. Try this yourself if you have\n> >> torvalds/linux.git locally:\n> >>\n> >> git clone --bare -s torvalds/linux.git test\n> >\n> > Yep, -s (--shared) makes cloning really cheap.  One of my goals is to get\n> >\n> > \tgit clone -s https://example.com/torvalds/linux.git\n> >\n> > and\n> >\n> > \tgit clone -s https://example.com/torvalds/linux.git/clone.bundle\n> >\n> > working.  That would make it easier for new contributors to\n> > setup lightweight clones and pull in history on an as-needed\n> > basis w/o hacks like shallow cloning.\n> \n> Does \"git clone --filter=blob:none\" do what you're looking for?\n\nOops, haven't seen that new feature :x  And haven't tried, pu @\n8d9027fa59b943db96a8a9090ec31d7f0f935596 is broken due to\nconflicts with hashmap (probably won't have time for a bit to\nlook at it).\n\nWhat I'm hoping to do with \"git clone -s\" would be client-only\nand compatible with existing HTTP servers that run\n\"git update-server-info\".\n"}]}