{"thread":{"id":"51025","subject":"","startedAt":"2019-05-03T08:16:08Z","lastAt":"2019-05-03T08:16:08Z","messageCount":1,"participants":["Eugeniu Rosca"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"374858","messageId":"20190503081558.GB4686@vmlxhi-102.adit-jv.com","threadId":"51025","inReplyTo":null,"subject":"","fromName":"Eugeniu Rosca","fromEmail":"erosca@de.adit-jv.com","sentAt":"2019-05-03T08:15:58Z","receivedAt":"2019-05-03T08:16:08Z","isPatch":false,"sender":{"key":"erosca@de.adit-jv.com","avatar":null},"body":"Bcc: \nSubject: Re: [PATCH 2/2] diffcore-pickaxe: add --pickaxe-raw-diff for use\n with -G\nReply-To: \nIn-Reply-To: <20190503031531.GA19436@sigill.intra.peff.net>\n\nOn Thu, May 02, 2019 at 11:15:31PM -0400, Jeff King wrote:\n> On Thu, Apr 25, 2019 at 02:54:48AM +0200, Eugeniu Rosca wrote:\n> \n> > > This is unrelated to --pickaxe-raw-diff, -U<n> just implies -p in\n> > > general. See e.g. \"git log -U1\".\n> > \n> > Oops. Since I use `-U<n>` mostly with `git show`, I missed the\n> > implication. You are right. Then, my question is how users are\n> > going to (quote from commit description):\n> > \n> > > >> > [..] search [..] through an arbitrary amount of\n> > > >> > context lines when combined with -U<n>.\n> > \n> > and achieve a `git log --oneline` report, given that -U<n> unfolds\n> > the commits?\n> \n> You can use \"-s\" to suppress patch output; as long as it comes after -U\n> on the command-line, it will countermand the patch-format part.\n\nThat's a handy trick. Now the feature is really usable. Thanks.\n\n> \n> (Of course it doesn't matter until we have a raw-diff grep, since\n> otherwise the context lines do not matter at all, and you should just\n> omit -U entirely).\n\nYep. Agreed.\n\n> \n> -Peff\n\n-- \nBest Regards,\nEugeniu.\n"}]}