{"thread":{"id":"20668","subject":"What's a good setup for submitting patches to the list properly?","startedAt":"2009-08-20T00:09:58Z","lastAt":"2009-08-25T00:14:09Z","messageCount":10,"participants":["Thell Fowler","Christian Couder","Nicolas Sebrecht","Julian Phillips"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"121303","messageId":"alpine.DEB.2.00.0908191849220.2012@GWPortableVCS","threadId":"20668","inReplyTo":null,"subject":"What's a good setup for submitting patches to the list properly?","fromName":"Thell Fowler","fromEmail":"git@tbfowler.name","sentAt":"2009-08-20T00:09:58Z","receivedAt":"2009-08-20T00:09:58Z","isPatch":false,"sender":{"key":"git@tbfowler.name","avatar":"https://gravatar.com/avatar/8b82510e07f3a8a77c8f41ce04c75c3b59b7e9c2d6f495b8f2ed834359efa6de?d=mp&s=160"},"body":"Sorry for once again.\n\nI haven't been able to figure out a good setup for posting patches to the \nlist correctly, perhaps someone could tell me where I'm going wrong.\n\nAlpine is setup to access git @ tbfowler.name with the 'postpone' folder \nbeing the 'Drafts' folder on the remote mail host, and a local mbox folder \n~/mail/git\n\nLocally I prepped the emails using:\n\ngit format-patch --cover-letter --full-index -n \n--in-reply-to=1249428804.2774.52.camel@GWPortableVCS --thread --signoff -6 \n--stdout>>~/mail/git\n\nhttp://article.gmane.org/gmane.comp.version-control.git/124834\n\nThinking that the cover letter would be in reply to a previous thread, and \nthat the rest would show as a reply to that.  After doing the \nformat-patch, I went into Alpine's git folder selected the messages and \nsaved them to the Drafts folder, then did 'compose' for each one, filling \nin the information I thought was needed.\n\nAt that point, the msg list looked flat, so I opened Evolution Mail and \nlooked at them there, they cascaded properly, so I sent them.  Yet, now, \nlooking on gmane each of the patch msgs is a top level post and the cover \nletter correctly posted as a reply to the previous thread.\n\nWhat could I have done/checked before sending to make sure that these \nwould have posted properly?\n\n-- \nThell\n"},{"id":"121517","messageId":"alpine.DEB.2.00.0908220953460.2012@GWPortableVCS","threadId":"20668","inReplyTo":"alpine.DEB.2.00.0908191849220.2012@GWPortableVCS","subject":"Re: What's a good setup for submitting patches to the list properly?","fromName":"Thell Fowler","fromEmail":"git@tbfowler.name","sentAt":"2009-08-22T15:01:22Z","receivedAt":"2009-08-22T15:01:22Z","isPatch":false,"sender":{"key":"git@tbfowler.name","avatar":"https://gravatar.com/avatar/8b82510e07f3a8a77c8f41ce04c75c3b59b7e9c2d6f495b8f2ed834359efa6de?d=mp&s=160"},"body":"Thell Fowler (git@tbfowler.name) wrote on Aug 19, 2009:\n\n> I haven't been able to figure out a good setup for posting patches to the \n> list correctly, perhaps someone could tell me where I'm going wrong.\n> \n> Alpine is setup to access git @ tbfowler.name with the 'postpone' folder \n> being the 'Drafts' folder on the remote mail host, and a local mbox folder \n> ~/mail/git\n> \n> Locally I prepped the emails using:\n> \n> git format-patch --cover-letter --full-index -n \n> --in-reply-to=1249428804.2774.52.camel@GWPortableVCS --thread --signoff -6 \n> --stdout>>~/mail/git\n> \n\nDid I miss something with that command?\n\n> http://article.gmane.org/gmane.comp.version-control.git/124834\n> \n> Thinking that the cover letter would be in reply to a previous thread, and \n> that the rest would show as a reply to that.  After doing the \n> format-patch, I went into Alpine's git folder selected the messages and \n> saved them to the Drafts folder, then did 'compose' for each one, filling \n> in the information I thought was needed.\n> \n\nPerhaps the saving to a new folder could've messed something up with the \nheaders?\n\n[snip]\n> What could I have done/checked before sending to make sure that these \n> would have posted properly?\n\nNo input on this?  Perhaps I should've posted to the git user or alpine \nlists?\n\nEither way, I'll be sending a new version of the patch I've been working \non and rather than have them show as top posts again I'd rather do it \ncorrectly.\n\nOr perhaps there is an easier more direct route...\n\n-- \nThell\n"},{"id":"121525","messageId":"200908222220.35354.chriscool@tuxfamily.org","threadId":"20668","inReplyTo":"alpine.DEB.2.00.0908220953460.2012@GWPortableVCS","subject":"Re: What's a good setup for submitting patches to the list properly?","fromName":"Christian Couder","fromEmail":"chriscool@tuxfamily.org","sentAt":"2009-08-22T20:20:35Z","receivedAt":"2009-08-22T20:20:35Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"On Saturday 22 August 2009, Thell Fowler wrote:\n>\n> > What could I have done/checked before sending to make sure that these\n> > would have posted properly?\n\nPerhaps you could send them to yourself.\n\n> No input on this?  Perhaps I should've posted to the git user or alpine\n> lists?\n\nIt's ok to post this kind of questions on the git mailing list.\n\nThere is \"git send-email\" that is bundled with git. But I use \ngit-mail-commits from Julian Philips. I am very happy with it. Thanks \nJulian!\n\nRegards,\nChristian.\n"},{"id":"121527","messageId":"20090822205656.GA3526@vidovic","threadId":"20668","inReplyTo":"200908222220.35354.chriscool@tuxfamily.org","subject":"git-mail-commits (Re: What's a good setup for submitting patches to the list properly?)","fromName":"Nicolas Sebrecht","fromEmail":"nicolas.s.dev@gmx.fr","sentAt":"2009-08-22T20:56:56Z","receivedAt":"2009-08-22T20:56:56Z","isPatch":false,"sender":{"key":"nicolas.s.dev@gmx.fr","avatar":null},"body":"The 22/08/09, Christian Couder wrote:\n\n> There is \"git send-email\" that is bundled with git. But I use \n> git-mail-commits from Julian Philips. I am very happy with it. Thanks \n> Julian!\n\nIsn't there any public repo for it?\n\n-- \nNicolas Sebrecht\n"},{"id":"121528","messageId":"alpine.DEB.2.00.0908221531230.29625@GWPortableVCS","threadId":"20668","inReplyTo":"200908222220.35354.chriscool@tuxfamily.org","subject":"Re: What's a good setup for submitting patches to the list properly?","fromName":"Thell Fowler","fromEmail":"git@tbfowler.name","sentAt":"2009-08-22T20:58:43Z","receivedAt":"2009-08-22T20:58:43Z","isPatch":false,"sender":{"key":"git@tbfowler.name","avatar":"https://gravatar.com/avatar/8b82510e07f3a8a77c8f41ce04c75c3b59b7e9c2d6f495b8f2ed834359efa6de?d=mp&s=160"},"body":"Christian Couder (chriscool@tuxfamily.org) wrote on Aug 22, 2009:\n\n> On Saturday 22 August 2009, Thell Fowler wrote:\n> >\n> > > What could I have done/checked before sending to make sure that these\n> > > would have posted properly?\n> \n> Perhaps you could send them to yourself.\n> \n\nYes, I did.  They all showed up under the correct thread, but then I \nchanged how I did it by adding cover-letter to the format-patch options.  \n\nBTW - After looking at the headers it looks like the cover letter header \nworked just fine, but that the cover letter msg-id changed between when \nformat-patch created it and when it was sent out causing the reset of the \nmsgs to not have anything to reference to.\n\n> > No input on this?  Perhaps I should've posted to the git user or alpine\n> > lists?\n> \n> It's ok to post this kind of questions on the git mailing list.\n> \n> There is \"git send-email\" that is bundled with git. But I use \n> git-mail-commits from Julian Philips. I am very happy with it. Thanks \n> Julian!\n> \n\nI guess I'll setup smtp and try the send-email route, not sure if that \nis going to change anything having to do with the In-Reply-To field \nand a cover letter or how it shows in the threading.\n\nIf that doesn't work then I'll give Julian's mail-commits a whirl.\n\nThanks for replying Christian!\n\n-- \nThell\n"},{"id":"121551","messageId":"200908230911.07218.chriscool@tuxfamily.org","threadId":"20668","inReplyTo":"20090822205656.GA3526@vidovic","subject":"Re: git-mail-commits (Re: What's a good setup for submitting patches to the list properly?)","fromName":"Christian Couder","fromEmail":"chriscool@tuxfamily.org","sentAt":"2009-08-23T07:11:06Z","receivedAt":"2009-08-23T07:11:06Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"On Saturday 22 August 2009, Nicolas Sebrecht wrote:\n> The 22/08/09, Christian Couder wrote:\n> > There is \"git send-email\" that is bundled with git. But I use\n> > git-mail-commits from Julian Philips. I am very happy with it. Thanks\n> > Julian!\n>\n> Isn't there any public repo for it?\n\nNot that I know of, but I think it would be a good idea to publish it \n(perhaps in contrib/).\n\nJulian?\n\nRegards,\nChristian.\n"},{"id":"121601","messageId":"alpine.LNX.2.00.0908232357590.15613@reaper.quantumfyre.co.uk","threadId":"20668","inReplyTo":"200908230911.07218.chriscool@tuxfamily.org","subject":"Re: git-mail-commits (Re: What's a good setup for submitting patches to the list properly?)","fromName":"Julian Phillips","fromEmail":"julian@quantumfyre.co.uk","sentAt":"2009-08-23T23:05:21Z","receivedAt":"2009-08-23T23:05:21Z","isPatch":false,"sender":{"key":"julian@quantumfyre.co.uk","avatar":"https://avatars.githubusercontent.com/u/948888?v=4"},"body":"On Sun, 23 Aug 2009, Christian Couder wrote:\n\n> On Saturday 22 August 2009, Nicolas Sebrecht wrote:\n>> The 22/08/09, Christian Couder wrote:\n>>> There is \"git send-email\" that is bundled with git. But I use\n>>> git-mail-commits from Julian Philips. I am very happy with it. Thanks\n>>> Julian!\n>>\n>> Isn't there any public repo for it?\n>\n> Not that I know of, but I think it would be a good idea to publish it\n> (perhaps in contrib/).\n>\n> Julian?\n\nUsing the awsome power of git I have managed to extract it from my random \ntools private repo to here as if I had written it to be a separate entity \nfrom the start:\n\ngit://git.q42.co.uk/mail_commits.git\n(gitweb: http://git.q42.co.uk/w/mail_commits.git)\n\nIf it would be considered useful, then I can also create a patch to add it \nto contrib (there is a master branch in the above repo where I have \nsubtree merged it in already - though that was more to experiment with \ndoing subtree merging)\n\n-- \nJulian\n\n  ---\nThe means-and-ends moralists, or non-doers, always end up on their ends\nwithout any means.\n \t\t-- Saul Alinsky\n"},{"id":"121602","messageId":"20090823234108.GB3526@vidovic","threadId":"20668","inReplyTo":"alpine.LNX.2.00.0908232357590.15613@reaper.quantumfyre.co.uk","subject":"Re: git-mail-commits (Re:What's a good setup for submitting patches to the list properly?)","fromName":"Nicolas Sebrecht","fromEmail":"nicolas.s.dev@gmx.fr","sentAt":"2009-08-23T23:41:08Z","receivedAt":"2009-08-23T23:41:08Z","isPatch":false,"sender":{"key":"nicolas.s.dev@gmx.fr","avatar":null},"body":"The 24/08/09, Julian Phillips wrote:\n> On Sun, 23 Aug 2009, Christian Couder wrote:\n>\n> Using the awsome power of git I have managed to extract it from my random \n> tools private repo to here as if I had written it to be a separate entity \n> from the start:\n>\n> git://git.q42.co.uk/mail_commits.git\n> (gitweb: http://git.q42.co.uk/w/mail_commits.git)\n\nThanks a lot.\n\n> If it would be considered useful, then I can also create a patch to add \n> it to contrib \n\nI think it worth. That said, I would first add some config options like\nmail-commits.cc (not reviewed that much yet) to be a bit more consistent\nwith the send-email program. I would also add README and INSTALL files.\n\nCould you please consider to place your code under GPLv2?\n\n-- \nNicolas Sebrecht\n"},{"id":"121687","messageId":"alpine.LNX.2.00.0908250102580.28400@reaper.quantumfyre.co.uk","threadId":"20668","inReplyTo":"20090823234108.GB3526@vidovic","subject":"Re: git-mail-commits (Re:What's a good setup for submitting patches to the list properly?)","fromName":"Julian Phillips","fromEmail":"julian@quantumfyre.co.uk","sentAt":"2009-08-25T00:06:30Z","receivedAt":"2009-08-25T00:06:30Z","isPatch":false,"sender":{"key":"julian@quantumfyre.co.uk","avatar":"https://avatars.githubusercontent.com/u/948888?v=4"},"body":"On Mon, 24 Aug 2009, Nicolas Sebrecht wrote:\n\n> The 24/08/09, Julian Phillips wrote:\n>> On Sun, 23 Aug 2009, Christian Couder wrote:\n>>\n>> Using the awsome power of git I have managed to extract it from my random\n>> tools private repo to here as if I had written it to be a separate entity\n>> from the start:\n>>\n>> git://git.q42.co.uk/mail_commits.git\n>> (gitweb: http://git.q42.co.uk/w/mail_commits.git)\n>\n> Thanks a lot.\n>\n>> If it would be considered useful, then I can also create a patch to add\n>> it to contrib\n>\n> I think it worth. That said, I would first add some config options like\n> mail-commits.cc (not reviewed that much yet) to be a bit more consistent\n> with the send-email program. I would also add README and INSTALL files.\n\nYeah ... it would be nice to have more options settable via config.  Some \nform of documentation would also be a good idea, and I would like to tidy \nthe code up a bit.  Kinda sort on tuits just at the moment though ... :(\n\n> Could you please consider to place your code under GPLv2?\n\nI have added a license statement.\n\n-- \nJulian\n\n  ---\nThus spake the master programmer:\n \t\"When a program is being tested, it is too late to make design changes.\"\n \t\t-- Geoffrey James, \"The Tao of Programming\"\n"},{"id":"121689","messageId":"20090825001409.GI3526@vidovic","threadId":"20668","inReplyTo":"alpine.LNX.2.00.0908250102580.28400@reaper.quantumfyre.co.uk","subject":"Re: git-mail-commits (Re:What's a good setup for submitting patches to the list properly?)","fromName":"Nicolas Sebrecht","fromEmail":"nicolas.s.dev@gmx.fr","sentAt":"2009-08-25T00:14:09Z","receivedAt":"2009-08-25T00:14:09Z","isPatch":false,"sender":{"key":"nicolas.s.dev@gmx.fr","avatar":null},"body":"The 25/08/09, Julian Phillips wrote:\n> On Mon, 24 Aug 2009, Nicolas Sebrecht wrote:\n>\n> > I think it worth. That said, I would first add some config options like\n> > mail-commits.cc (not reviewed that much yet) to be a bit more consistent\n> > with the send-email program. I would also add README and INSTALL files.\n>\n> Yeah ... it would be nice to have more options settable via config.  Some \n> form of documentation would also be a good idea, and I would like to tidy \n> the code up a bit.  Kinda sort on tuits just at the moment though ... :(\n\nWill have help from me. I find it nice to have a python alternative to\nsend-email. ,-p\n\n> > Could you please consider to place your code under GPLv2?\n>\n> I have added a license statement.\n\nThank you. Patches comming.\n\n-- \nNicolas Sebrecht\n"}]}