git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Catalin Marinas" <catalin.marinas@gmail.com>
To: "Yann Dirson" <ydirson@altern.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 4/4] Add new --diff-opts/-O flag to diff- and status-related commands.
Date: Mon, 4 Jun 2007 23:15:23 +0100	[thread overview]
Message-ID: <b0943d9e0706041515l6114a015ye45d40478cc0e3ef@mail.gmail.com> (raw)
In-Reply-To: <20070531223438.6005.76115.stgit@gandelf.nowhere.earth>

On 31/05/07, Yann Dirson <ydirson@altern.org> wrote:
> This new flag allows to pass arbitrary flags to the git-diff calls
> underlying several StGIT commands.  It can be used to pass flags
> affecting both diff- and status-generating commands (eg. -M or -C), or
> flags only affecting diff-generating ones (eg. --color, --binary).
>
> It supercedes --binary for commands where it was allowed,
> '-O --binary' is now available for the same functionality.

BTW, should we add --binary by default to export and mail? Do you see
any problem with this?

Another idea would be to add support for a [stgit "options"] section
with entries like "mail = -O --binary".

-- 
Catalin

  reply	other threads:[~2007-06-04 22:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-31 22:34 [StGIT PATCH 0/4] Rename detection, take 2 Yann Dirson
2007-05-31 22:34 ` [PATCH 1/4] Add 2 new contrib scripts Yann Dirson
2007-06-01  9:22   ` David Kågedal
2007-06-03 12:32     ` Karl Hasselström
2007-06-03 12:40       ` Yann Dirson
2007-05-31 22:34 ` [PATCH 2/4] Call external commands without a shell where possible Yann Dirson
2007-05-31 22:34 ` [PATCH 3/4] Make diff flags handling more modular Yann Dirson
2007-05-31 22:34 ` [PATCH 4/4] Add new --diff-opts/-O flag to diff- and status-related commands Yann Dirson
2007-06-04 22:15   ` Catalin Marinas [this message]
2007-06-05  6:47     ` Yann Dirson

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=b0943d9e0706041515l6114a015ye45d40478cc0e3ef@mail.gmail.com \
    --to=catalin.marinas@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=ydirson@altern.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).