{"thread":{"id":"54050","subject":"[RFC 0/3] support negative refspecs","startedAt":"2020-08-15T00:28:51Z","lastAt":"2020-08-15T21:55:39Z","messageCount":2,"participants":["Jacob Keller"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"403736","messageId":"20200815002831.2468968-1-jacob.e.keller@intel.com","threadId":"54050","inReplyTo":null,"subject":"[RFC 0/3] support negative refspecs","fromName":"Jacob Keller","fromEmail":"jacob.e.keller@intel.com","sentAt":"2020-08-15T00:28:31Z","receivedAt":"2020-08-15T00:28:51Z","isPatch":false,"sender":{"key":"jacob.e.keller@intel.com","avatar":"https://avatars.githubusercontent.com/u/874719?v=4"},"body":"From: Jacob Keller <jacob.keller@gmail.com>\n\nThis is more or less just a port of what Peff already had published a few\nyears ago at https://lore.kernel.org/git/20140125013433.GA22336@sigill.intra.peff.net/\n\nI cleaned some things up and made sure the tests pass, but haven't yet added\nany new tests.\n\nI think the overal design makes sense: applying positive first and then\nnegative. This appears to be how negative pathspecs work at least as far as\nI could tell with a few trials.\n\nThe first two patches are cleanup/fixups that I think could go separately if\neveryone agrees. The third is the meat of the idea, and where most of the\nwork needs to be done.\n\nJacob Keller (3):\n  refspec: fix documentation referring to refspec_item\n  refspec: make sure stack refspec_item variables are zeroed\n  refspec: add support for negative refspecs\n\n builtin/fetch.c  |  3 +++\n builtin/remote.c |  1 +\n refspec.c        | 30 +++++++++++++++++++++++++++++\n refspec.h        | 29 +++++++++++++++-------------\n remote.c         | 49 +++++++++++++++++++++++++++++++++++++++++++++++-\n remote.h         |  9 ++++++++-\n transport.c      |  1 +\n 7 files changed, 107 insertions(+), 15 deletions(-)\n\n\nbase-commit: 878e727637ec5815ccb3301eb994a54df95b21b8\n-- \n2.28.0.163.g6104cc2f0b60\n\n"},{"id":"403745","messageId":"CA+P7+xoDckBukFF9MnkhmWDdJxEcCZK5jg6HJcBbPcXB70xOUQ@mail.gmail.com","threadId":"54050","inReplyTo":"20200815002831.2468968-1-jacob.e.keller@intel.com","subject":"Re: [RFC 0/3] support negative refspecs","fromName":"Jacob Keller","fromEmail":"jacob.keller@gmail.com","sentAt":"2020-08-15T00:29:45Z","receivedAt":"2020-08-15T21:55:39Z","isPatch":false,"sender":{"key":"jacob.keller@gmail.com","avatar":"https://avatars.githubusercontent.com/u/874719?v=4"},"body":"On Fri, Aug 14, 2020 at 5:28 PM Jacob Keller <jacob.e.keller@intel.com> wrote:\n>\n> From: Jacob Keller <jacob.keller@gmail.com>\n>\n> This is more or less just a port of what Peff already had published a few\n> years ago at https://lore.kernel.org/git/20140125013433.GA22336@sigill.intra.peff.net/\n>\n> I cleaned some things up and made sure the tests pass, but haven't yet added\n> any new tests.\n>\n> I think the overal design makes sense: applying positive first and then\n> negative. This appears to be how negative pathspecs work at least as far as\n> I could tell with a few trials.\n>\n> The first two patches are cleanup/fixups that I think could go separately if\n> everyone agrees. The third is the meat of the idea, and where most of the\n> work needs to be done.\n>\n> Jacob Keller (3):\n>   refspec: fix documentation referring to refspec_item\n>   refspec: make sure stack refspec_item variables are zeroed\n>   refspec: add support for negative refspecs\n>\n>  builtin/fetch.c  |  3 +++\n>  builtin/remote.c |  1 +\n>  refspec.c        | 30 +++++++++++++++++++++++++++++\n>  refspec.h        | 29 +++++++++++++++-------------\n>  remote.c         | 49 +++++++++++++++++++++++++++++++++++++++++++++++-\n>  remote.h         |  9 ++++++++-\n>  transport.c      |  1 +\n>  7 files changed, 107 insertions(+), 15 deletions(-)\n>\n>\n> base-commit: 878e727637ec5815ccb3301eb994a54df95b21b8\n> --\n> 2.28.0.163.g6104cc2f0b60\n>\n\nThis probably doesn't have the right reply headers, because I forgot\nto send the cover letter along with the patches and realized it after\nI hit send. Sorry!\n\nThanks,\nJake\n"}]}