From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] Write diff output to a file in struct diff_options
Date: Mon, 10 Mar 2008 12:52:44 +0100 [thread overview]
Message-ID: <fr37ec$9k4$1@ger.gmane.org> (raw)
In-Reply-To: alpine.LNX.1.00.0803092235150.19665@iabervon.org
Daniel Barkalow wrote:
> I remember there being some expectation that this would be difficult, but
> it was a pretty straightforward conversion, so I'm wondering if I've
> missed something. In any case, this is missing tests and documentation for
> --output=, but I really want it to use directly for rebase-interactive,
> and I only did the command line option so I could do informal testing.
>
> diff.c | 306 +++++++++++++++++++++++++++++++++++-----------------------------
> diff.h | 3 +
> 2 files changed, 169 insertions(+), 140 deletions(-)
Errr... where is the documentation?
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2008-03-10 11:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-10 2:43 [PATCH] Write diff output to a file in struct diff_options Daniel Barkalow
2008-03-10 6:18 ` Junio C Hamano
2008-03-10 11:06 ` Johannes Schindelin
2008-03-10 11:52 ` Jakub Narebski [this message]
2008-03-10 12:29 ` Johannes Schindelin
2008-03-10 17:58 ` Kristian Høgsberg
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='fr37ec$9k4$1@ger.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
/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.
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 NNTP newsgroup(s).