{"thread":{"id":"34465","subject":"Git tag output order is incorrect (IMHO)","startedAt":"2013-07-18T15:27:00Z","lastAt":"2013-10-16T18:06:19Z","messageCount":16,"participants":["Rahul Bansal","Duy Nguyen","Andreas Schwab","Junio C Hamano","Jeff King","Antoine Pelisse","Felipe Contreras","Phil Hord"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"223650","messageId":"840FACA0-7E13-41DB-A0F8-124FAB53BFBD@rtcamp.com","threadId":"34465","inReplyTo":null,"subject":"Git tag output order is incorrect (IMHO)","fromName":"Rahul Bansal","fromEmail":"rahul.bansal@rtcamp.com","sentAt":"2013-07-18T15:27:00Z","receivedAt":"2013-07-18T15:27:00Z","isPatch":false,"sender":{"key":"rahul.bansal@rtcamp.com","avatar":"https://gravatar.com/avatar/f5fb22fa04c0f3c66f6326ca4bef748cdca1be299ee3daaeaa5e0b754f41ca38?d=mp&s=160"},"body":"I am posting here first time, so please excuse me if this is not right place to send something like this.\n\nPlease check - http://stackoverflow.com/questions/6091306/can-i-make-git-print-x-y-z-style-tag-names-in-a-sensible-order\n\nAnd also - https://github.com/gitlabhq/gitlabhq/issues/4565\n\nIMHO \"git tag\" is expected to show tag-list ordered by versions. \n\nIt may be case, that people do not follow same version numbering convention. Most people after x.9.x increment major version (that is why they may not be affected because of this)\n\nAnother option like \"git tag --date-asc\" can be added which will print tags by creation date. (As long as people do not create backdated tag, this will work).\n\nThanks,\n-Rahul"},{"id":"223651","messageId":"CACsJy8CpZHTCr0=MkSpfurPW_fyLGN_zd4uSzvBSYbuqH8aXew@mail.gmail.com","threadId":"34465","inReplyTo":"840FACA0-7E13-41DB-A0F8-124FAB53BFBD@rtcamp.com","subject":"Re: Git tag output order is incorrect (IMHO)","fromName":"Duy Nguyen","fromEmail":"pclouds@gmail.com","sentAt":"2013-07-18T15:51:55Z","receivedAt":"2013-07-18T15:51:55Z","isPatch":false,"sender":{"key":"pclouds@gmail.com","avatar":"https://avatars.githubusercontent.com/u/720?v=4"},"body":"On Thu, Jul 18, 2013 at 10:27 PM, Rahul Bansal wrote:\n> I am posting here first time, so please excuse me if this is not right place to send something like this.\n>\n> Please check - http://stackoverflow.com/questions/6091306/can-i-make-git-print-x-y-z-style-tag-names-in-a-sensible-order\n>\n> And also - https://github.com/gitlabhq/gitlabhq/issues/4565\n>\n> IMHO \"git tag\" is expected to show tag-list ordered by versions.\n>\n> It may be case, that people do not follow same version numbering convention. Most people after x.9.x increment major version (that is why they may not be affected because of this)\n>\n> Another option like \"git tag --date-asc\" can be added which will print tags by creation date. (As long as people do not create backdated tag, this will work).\n\nTry\n\ngit for-each-ref --sort=committerdate --format='%(refname:short)' refs/tags\n--\nDuy\n"},{"id":"223652","messageId":"CACsJy8Av7b9GMuO-HsT_+QHAc3iDUZQk5KdJ=p8VugaYc3nUPg@mail.gmail.com","threadId":"34465","inReplyTo":"CACsJy8CpZHTCr0=MkSpfurPW_fyLGN_zd4uSzvBSYbuqH8aXew@mail.gmail.com","subject":"Re: Git tag output order is incorrect (IMHO)","fromName":"Duy Nguyen","fromEmail":"pclouds@gmail.com","sentAt":"2013-07-18T15:56:37Z","receivedAt":"2013-07-18T15:56:37Z","isPatch":false,"sender":{"key":"pclouds@gmail.com","avatar":"https://avatars.githubusercontent.com/u/720?v=4"},"body":"On Thu, Jul 18, 2013 at 10:51 PM, Duy Nguyen wrote:\n> Try\n>\n> git for-each-ref --sort=committerdate --format='%(refname:short)' refs/tags\n\nAnd I wondered why it did not seem right. Use this one instead\n\ngit for-each-ref --sort=taggerdate --format='%(refname:short)' refs/tags\n\nmake it --sort=-taggerdate to reverse sort order.\n--\nDuy\n"},{"id":"223653","messageId":"CADtAFQ=DwTHv3n56xoTEN7JmwT+b3Bv0CdR_nBbyYudgoCmZUA@mail.gmail.com","threadId":"34465","inReplyTo":"CACsJy8CpZHTCr0=MkSpfurPW_fyLGN_zd4uSzvBSYbuqH8aXew@mail.gmail.com","subject":"Re: Git tag output order is incorrect (IMHO)","fromName":"Rahul Bansal","fromEmail":"rahul.bansal@rtcamp.com","sentAt":"2013-07-18T15:57:07Z","receivedAt":"2013-07-18T15:57:07Z","isPatch":false,"sender":{"key":"rahul.bansal@rtcamp.com","avatar":"https://gravatar.com/avatar/f5fb22fa04c0f3c66f6326ca4bef748cdca1be299ee3daaeaa5e0b754f41ca38?d=mp&s=160"},"body":"Hi Day,\n\nI am aware of that command as well.\n\nI think `git tag` current default order is string-based sorting. I\nfelt version-number based sorting and/or create-date based sorting\nwill be more appropriate.\n\n--\nRahul Bansal | Founder & CEO | rtCamp Solutions Pvt. Ltd.\nSkype: rahul286 | Twitter: @rahul286 | Web: http://rtcamp.com/\n\n\nOn Thu, Jul 18, 2013 at 9:21 PM, Duy Nguyen wrote:\n>\n> On Thu, Jul 18, 2013 at 10:27 PM, Rahul Bansal \n> wrote:\n> > I am posting here first time, so please excuse me if this is not right\n> > place to send something like this.\n> >\n> > Please check -\n> > http://stackoverflow.com/questions/6091306/can-i-make-git-print-x-y-z-style-tag-names-in-a-sensible-order\n> >\n> > And also - https://github.com/gitlabhq/gitlabhq/issues/4565\n> >\n> > IMHO \"git tag\" is expected to show tag-list ordered by versions.\n> >\n> > It may be case, that people do not follow same version numbering\n> > convention. Most people after x.9.x increment major version (that is why\n> > they may not be affected because of this)\n> >\n> > Another option like \"git tag --date-asc\" can be added which will print\n> > tags by creation date. (As long as people do not create backdated tag, this\n> > will work).\n>\n> Try\n>\n> git for-each-ref --sort=committerdate --format='%(refname:short)'\n> refs/tags\n> --\n> Duy\n"},{"id":"223654","messageId":"CADtAFQk3inn2C6s0f-uc55Y=wPvwAtmgRu67D9uw6pcMxLvWmA@mail.gmail.com","threadId":"34465","inReplyTo":"CACsJy8Av7b9GMuO-HsT_+QHAc3iDUZQk5KdJ=p8VugaYc3nUPg@mail.gmail.com","subject":"Re: Git tag output order is incorrect (IMHO)","fromName":"Rahul Bansal","fromEmail":"rahul.bansal@rtcamp.com","sentAt":"2013-07-18T15:58:11Z","receivedAt":"2013-07-18T15:58:11Z","isPatch":false,"sender":{"key":"rahul.bansal@rtcamp.com","avatar":"https://gravatar.com/avatar/f5fb22fa04c0f3c66f6326ca4bef748cdca1be299ee3daaeaa5e0b754f41ca38?d=mp&s=160"},"body":"Thanks again Duy. :-)\n\nSorry for misspelling your name in earlier email.\n--\nRahul Bansal | Founder & CEO | rtCamp Solutions Pvt. Ltd.\nSkype: rahul286 | Twitter: @rahul286 | Web: http://rtcamp.com/\n\n\nOn Thu, Jul 18, 2013 at 9:26 PM, Duy Nguyen wrote:\n> On Thu, Jul 18, 2013 at 10:51 PM, Duy Nguyen wrote:\n>> Try\n>>\n>> git for-each-ref --sort=committerdate --format='%(refname:short)' refs/tags\n>\n> And I wondered why it did not seem right. Use this one instead\n>\n> git for-each-ref --sort=taggerdate --format='%(refname:short)' refs/tags\n>\n> make it --sort=-taggerdate to reverse sort order.\n> --\n> Duy\n"},{"id":"223655","messageId":"CACsJy8DSYPn+ZkyS+Ufs5QPvfQ1OzkWYB--1gWZQackkeFkyyw@mail.gmail.com","threadId":"34465","inReplyTo":"CADtAFQ=DwTHv3n56xoTEN7JmwT+b3Bv0CdR_nBbyYudgoCmZUA@mail.gmail.com","subject":"Re: Git tag output order is incorrect (IMHO)","fromName":"Duy Nguyen","fromEmail":"pclouds@gmail.com","sentAt":"2013-07-18T16:14:54Z","receivedAt":"2013-07-18T16:14:54Z","isPatch":false,"sender":{"key":"pclouds@gmail.com","avatar":"https://avatars.githubusercontent.com/u/720?v=4"},"body":"On Thu, Jul 18, 2013 at 10:57 PM, Rahul Bansal wrote:\n> Hi Day,\n>\n> I am aware of that command as well.\n>\n> I think `git tag` current default order is string-based sorting. I\n> felt version-number based sorting and/or create-date based sorting\n> will be more appropriate.\n\nok you mean the _default_ order? What about other non-version tags\n(even temporary ones just to mark something then removed)?\n--\nDuy\n"},{"id":"223667","messageId":"87wqon7ok4.fsf@igel.home","threadId":"34465","inReplyTo":"840FACA0-7E13-41DB-A0F8-124FAB53BFBD@rtcamp.com","subject":"Re: Git tag output order is incorrect (IMHO)","fromName":"Andreas Schwab","fromEmail":"schwab@linux-m68k.org","sentAt":"2013-07-18T17:42:03Z","receivedAt":"2013-07-18T17:42:03Z","isPatch":false,"sender":{"key":"schwab@linux-m68k.org","avatar":"https://avatars.githubusercontent.com/u/2175493?v=4"},"body":"Rahul Bansal writes:\n\n> IMHO \"git tag\" is expected to show tag-list ordered by versions. \n\nA git tag can be anything, not related to versions at all.\n\nAndreas.\n\n-- \nAndreas Schwab, schwab@linux-m68k.org\nGPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5\n\"And now for something completely different.\"\n"},{"id":"223798","messageId":"7vli52uym0.fsf@alter.siamese.dyndns.org","threadId":"34465","inReplyTo":"87wqon7ok4.fsf@igel.home","subject":"Re: Git tag output order is incorrect (IMHO)","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2013-07-19T19:40:55Z","receivedAt":"2013-07-19T19:40:55Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Andreas Schwab writes:\n\n> Rahul Bansal writes:\n>\n>> IMHO \"git tag\" is expected to show tag-list ordered by versions. \n>\n> A git tag can be anything, not related to versions at all.\n\nCorrect.\n\nBut that does not prevent somebody to add \"git tag --sort=X\" option\nto the command, just like \"git for-each-ref\" has \"--sort=X\" option.\n"},{"id":"223820","messageId":"20130720002241.GA22143@sigill.intra.peff.net","threadId":"34465","inReplyTo":"7vli52uym0.fsf@alter.siamese.dyndns.org","subject":"Re: Git tag output order is incorrect (IMHO)","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2013-07-20T00:22:41Z","receivedAt":"2013-07-20T00:22:41Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Fri, Jul 19, 2013 at 12:40:55PM -0700, Junio C Hamano wrote:\n\n> Andreas Schwab writes:\n> \n> > Rahul Bansal writes:\n> >\n> >> IMHO \"git tag\" is expected to show tag-list ordered by versions. \n> >\n> > A git tag can be anything, not related to versions at all.\n> \n> Correct.\n> \n> But that does not prevent somebody to add \"git tag --sort=X\" option\n> to the command, just like \"git for-each-ref\" has \"--sort=X\" option.\n\nA while ago I started on (but did not get very far on) unifying the ref\nselection code for for-each-ref, tag, and branch. It would be nice if\nthey all supported the same set of --contains/--points-at/--merged/--sort,\netc.\n\nI do plan to finish it eventually, but if anyone else feels like picking\nit up, I'd be glad to review patches and/or share my work-in-progress as\na starting point.\n\n-Peff\n"},{"id":"225523","messageId":"CALWbr2w7XCuD5tUSwR+Cwv4wyXLk8MHDGyU2Dr+jA9vOfDYqig@mail.gmail.com","threadId":"34465","inReplyTo":"20130720002241.GA22143@sigill.intra.peff.net","subject":"Re: Git tag output order is incorrect (IMHO)","fromName":"Antoine Pelisse","fromEmail":"apelisse@gmail.com","sentAt":"2013-08-20T15:12:47Z","receivedAt":"2013-08-20T15:12:47Z","isPatch":false,"sender":{"key":"apelisse@gmail.com","avatar":"https://avatars.githubusercontent.com/u/1929644?v=4"},"body":"On Sat, Jul 20, 2013 at 2:22 AM, Jeff King wrote:\n> I do plan to finish it eventually, but if anyone else feels like picking\n> it up, I'd be glad to review patches and/or share my work-in-progress as\n> a starting point.\n\nHi Jeff,\nI have some free time to come, and would like to work on that feature.\nDoes the offer still hold ?\nIf it does, I would be interested in your patches.\n\nCheers,\n"},{"id":"227103","messageId":"20130908080311.GA25498@sigill.intra.peff.net","threadId":"34465","inReplyTo":"CALWbr2w7XCuD5tUSwR+Cwv4wyXLk8MHDGyU2Dr+jA9vOfDYqig@mail.gmail.com","subject":"Re: Git tag output order is incorrect (IMHO)","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2013-09-08T08:03:11Z","receivedAt":"2013-09-08T08:03:11Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Tue, Aug 20, 2013 at 05:12:47PM +0200, Antoine Pelisse wrote:\n\n> On Sat, Jul 20, 2013 at 2:22 AM, Jeff King wrote:\n> > I do plan to finish it eventually, but if anyone else feels like picking\n> > it up, I'd be glad to review patches and/or share my work-in-progress as\n> > a starting point.\n> \n> I have some free time to come, and would like to work on that feature.\n> Does the offer still hold ?\n> If it does, I would be interested in your patches.\n\nI'm sorry I have taken so long to get back to you on this. I was hoping\nto revisit the topic and make sure the patches were in a sensible state\nfor showing to somebody. But it took me some time to get around to it,\nand now that I have, they're really not looking very good.\n\nMy general strategy was to factor out all of the \"which refs to select\"\ncode from git-tag (which knows --contains and --points-at) and\ngit-branch (which knows --merged, --no-merged, and --contains), and then\nmake them all available in a library-ish way to both commands, as well\nas for-each-ref (which also knows name matching, which all 3 should\nknow, too). You can see my messy in-progress commit (that does not even\ncompile) at:\n\n git://github.com/peff/git.git jk/contains-wip\n\nPart of the complication is that the filters have to happen at different\ntimes (you can efficiently ask \"--contains\" for each ref as you see it,\nbut asking \"--merged\" must happen after you have collected each one).\n\nI do not recall at this point what other issues led me to stop working\non it (it may simply have been time for dinner, and I never came back to\nit). So the patches there may or may not actually be helpful to you.\n\nSorry I can't be more helpful. I'd be happy to discuss or review if you\nwant to work on it.\n\n-Peff\n"},{"id":"227163","messageId":"CAMP44s3p_DRTvBhKbM0ejKgea9hauSCzahPux4jCWL7JP4nxKw@mail.gmail.com","threadId":"34465","inReplyTo":"840FACA0-7E13-41DB-A0F8-124FAB53BFBD@rtcamp.com","subject":"Re: Git tag output order is incorrect (IMHO)","fromName":"Felipe Contreras","fromEmail":"felipe.contreras@gmail.com","sentAt":"2013-09-08T22:49:41Z","receivedAt":"2013-09-08T22:49:41Z","isPatch":false,"sender":{"key":"felipe.contreras@gmail.com","avatar":"https://avatars.githubusercontent.com/u/8358?v=4"},"body":"On Thu, Jul 18, 2013 at 10:27 AM, Rahul Bansal wrote:\n> I am posting here first time, so please excuse me if this is not right place to send something like this.\n>\n> Please check - http://stackoverflow.com/questions/6091306/can-i-make-git-print-x-y-z-style-tag-names-in-a-sensible-order\n>\n> And also - https://github.com/gitlabhq/gitlabhq/issues/4565\n>\n> IMHO \"git tag\" is expected to show tag-list ordered by versions.\n>\n> It may be case, that people do not follow same version numbering convention. Most people after x.9.x increment major version (that is why they may not be affected because of this)\n>\n> Another option like \"git tag --date-asc\" can be added which will print tags by creation date. (As long as people do not create backdated tag, this will work).\n\nI completely agree, and there was a proposal to an option like this a\nlong time ago:\n\nhttp://article.gmane.org/gmane.comp.version-control.git/111032\n\n-- \nFelipe Contreras\n"},{"id":"227449","messageId":"CABURp0o5tOswiv_avfAQOZwGREpX3v7MwcdVzt7dkubY2Y0O6g@mail.gmail.com","threadId":"34465","inReplyTo":"CAMP44s3p_DRTvBhKbM0ejKgea9hauSCzahPux4jCWL7JP4nxKw@mail.gmail.com","subject":"Re: Git tag output order is incorrect (IMHO)","fromName":"Phil Hord","fromEmail":"phil.hord@gmail.com","sentAt":"2013-09-11T13:42:27Z","receivedAt":"2013-09-11T13:42:27Z","isPatch":false,"sender":{"key":"phil.hord@gmail.com","avatar":"https://avatars.githubusercontent.com/u/123908?v=4"},"body":"Someone at $work asked me this week how to find the current and\nprevious tags on his branch so he could generate release notes. I\njust need \"last two tags on head in topo-order\". I was surprised by\nhow complicated this turned out to be. I ended up with this:\n\n git log --decorate=full --pretty=format:'%d' HEAD |\n sed -n -e 's-^.* refs/tags/\\(.*\\)[ )].*$-\\1-p' |\n head -2\n\nSurely there's a cleaner way, right?\n\nPhil\n\n\n\nOn Sun, Sep 8, 2013 at 6:49 PM, Felipe Contreras\n wrote:\n> On Thu, Jul 18, 2013 at 10:27 AM, Rahul Bansal wrote:\n>> I am posting here first time, so please excuse me if this is not right place to send something like this.\n>>\n>> Please check - http://stackoverflow.com/questions/6091306/can-i-make-git-print-x-y-z-style-tag-names-in-a-sensible-order\n>>\n>> And also - https://github.com/gitlabhq/gitlabhq/issues/4565\n>>\n>> IMHO \"git tag\" is expected to show tag-list ordered by versions.\n>>\n>> It may be case, that people do not follow same version numbering convention. Most people after x.9.x increment major version (that is why they may not be affected because of this)\n>>\n>> Another option like \"git tag --date-asc\" can be added which will print tags by creation date. (As long as people do not create backdated tag, this will work).\n>\n> I completely agree, and there was a proposal to an option like this a\n> long time ago:\n>\n> http://article.gmane.org/gmane.comp.version-control.git/111032\n>\n> --\n> Felipe Contreras\n> --\n> To unsubscribe from this list: send the line \"unsubscribe git\" in\n> the body of a message to majordomo@vger.kernel.org\n> More majordomo info at http://vger.kernel.org/majordomo-info.html\n"},{"id":"227471","messageId":"xmqqioy7tfba.fsf@gitster.dls.corp.google.com","threadId":"34465","inReplyTo":"CABURp0o5tOswiv_avfAQOZwGREpX3v7MwcdVzt7dkubY2Y0O6g@mail.gmail.com","subject":"Re: Git tag output order is incorrect (IMHO)","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2013-09-11T17:54:01Z","receivedAt":"2013-09-11T17:54:01Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Phil Hord writes:\n\n> Someone at $work asked me this week how to find the current and\n> previous tags on his branch so he could generate release notes. I\n> just need \"last two tags on head in topo-order\". I was surprised by\n> how complicated this turned out to be. I ended up with this:\n>\n> git log --decorate=full --pretty=format:'%d' HEAD |\n> sed -n -e 's-^.* refs/tags/\\(.*\\)[ )].*$-\\1-p' |\n> head -2\n>\n> Surely there's a cleaner way, right?\n\nThat looks clean enough (I would have used \"head -n 2\" though) and\nin line with the way how you can exercise the flexibility of the\nsystem, at least to me ;-).\n\nJoking aside, I agree that a \"--merged X\" primitive, i.e. \"what refs\ncan be reachable from commit X?\", in the listing mode of \"git tag\"\nor \"git for-each-ref\" would have helped. As the sorting and\nformatting primitives are already there in for-each-ref, it would\nhave been\n\n\tgit for-each-ref \\\n --format='%(refname:short)' \\\n --sort='-*committerdate' \\\n --count=2 \\\n --merged my-branch \\\n refs/tags/\n\nor something like that.\n"},{"id":"229075","messageId":"20131016175621.GA4308@sigill.intra.peff.net","threadId":"34465","inReplyTo":"20130908080311.GA25498@sigill.intra.peff.net","subject":"Re: Git tag output order is incorrect (IMHO)","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2013-10-16T17:56:21Z","receivedAt":"2013-10-16T17:56:21Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Sun, Sep 08, 2013 at 04:03:11AM -0400, Jeff King wrote:\n\n> > I have some free time to come, and would like to work on that feature.\n> > Does the offer still hold ?\n> > If it does, I would be interested in your patches.\n> \n> I'm sorry I have taken so long to get back to you on this. I was hoping\n> to revisit the topic and make sure the patches were in a sensible state\n> for showing to somebody. But it took me some time to get around to it,\n> and now that I have, they're really not looking very good.\n\nHi Antoine,\n\nSince I haven't heard anything, I assume you haven't been working on\nthis. But in case you have, I wanted to let you know I found some time\nand moved the topic forward a bit. It's not quite ready to share with\nthe list, but I wanted to notify you so we didn't duplicate effort.\n\n-Peff\n"},{"id":"229076","messageId":"CALWbr2zMrUL0cmtYuoGZ_Sm33i29fJRdJtDZmd6kR_KrabU+PQ@mail.gmail.com","threadId":"34465","inReplyTo":"20131016175621.GA4308@sigill.intra.peff.net","subject":"Re: Git tag output order is incorrect (IMHO)","fromName":"Antoine Pelisse","fromEmail":"apelisse@gmail.com","sentAt":"2013-10-16T18:06:19Z","receivedAt":"2013-10-16T18:06:19Z","isPatch":false,"sender":{"key":"apelisse@gmail.com","avatar":"https://avatars.githubusercontent.com/u/1929644?v=4"},"body":"On Wed, Oct 16, 2013 at 7:56 PM, Jeff King wrote:\n> On Sun, Sep 08, 2013 at 04:03:11AM -0400, Jeff King wrote:\n>\n>> > I have some free time to come, and would like to work on that feature.\n>> > Does the offer still hold ?\n>> > If it does, I would be interested in your patches.\n>>\n>> I'm sorry I have taken so long to get back to you on this. I was hoping\n>> to revisit the topic and make sure the patches were in a sensible state\n>> for showing to somebody. But it took me some time to get around to it,\n>> and now that I have, they're really not looking very good.\n>\n> Hi Antoine,\n>\n> Since I haven't heard anything, I assume you haven't been working on\n> this. But in case you have, I wanted to let you know I found some time\n> and moved the topic forward a bit. It's not quite ready to share with\n> the list, but I wanted to notify you so we didn't duplicate effort.\n\nUnfortunately, I didn't have as much time as expected to work on this topic.\nI'm glad to hear that it's moving forward and will definitely have a\nlook when you send the patches to the list.\nThank you for letting me know,\n\nCheers,\nAntoine\n"}]}