From: Dennis Kaarsemaker <dennis@kaarsemaker.net>
To: "Martin Ågren" <martin.agren@gmail.com>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: Git diff --no-index and file descriptor inputs
Date: Tue, 24 Oct 2017 15:39:24 +0200 [thread overview]
Message-ID: <1508852364.2750.31.camel@kaarsemaker.net> (raw)
In-Reply-To: <F65D91595838434A963FC2EE26D62CB8@blackfat>
On Thu, 2017-09-07 at 15:55 -0400, Jason Pyeron wrote:
> > -----Original Message-----
> > From: Martin Ågren
> > Sent: Thursday, September 7, 2017 1:48 PM
> >
> > On 7 September 2017 at 18:00, Jason Pyeron <jpyeron@pdinc.us> wrote:
> > >
> > > I was hoping to leverage --word-diff-regex, but the
> >
> > --no-index option
> > > does not seem to work with <(...) notation.
> > >
> > > I am I doing something wrong or is this a bug?
> >
> > There were some patches floating around half a year ago, I
> > don't know what happened to them.
> >
> > From: Dennis Kaarsemaker
> > Sent: Friday, January 13, 2017 5:20 AM
> > Subject: [PATCH v2 0/2] diff --no-index: support symlinks and pipes
> > https://public-inbox.org/git/20170324213110.4331-1-dennis@kaarsemaker.net/
>
> I see, it goes back to 2016...
>
> > From: Dennis Kaarsemaker
> > Subject: [RFC/PATCH 0/2] git diff <(command1) <(command2)
> > Date: Fri, 11 Nov 2016 21:19:56 +0100
>
> https://public-inbox.org/git/20161111201958.2175-1-dennis@kaarsemaker.net/
>
> I will read up on those threads weekend, then try to apply the patches and
> see what happens.
>
> Thanks for the google fu help.
I hope to send a new version of this soon. I had almost no time to do
anything git related in the last year, trying to catch up with mailing
list traffic now.
D.
prev parent reply other threads:[~2017-10-24 13:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-07 16:00 Git diff --no-index and file descriptor inputs Jason Pyeron
2017-09-07 17:47 ` Martin Ågren
2017-09-07 19:55 ` Jason Pyeron
2017-10-24 13:39 ` Dennis Kaarsemaker [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1508852364.2750.31.camel@kaarsemaker.net \
--to=dennis@kaarsemaker.net \
--cc=git@vger.kernel.org \
--cc=martin.agren@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).