All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jon Loeliger <jdl@jdl.com>, git@vger.kernel.org
Subject: Re: Dubious format-patch options
Date: Thu, 12 Jun 2008 20:01:45 -0700	[thread overview]
Message-ID: <7vtzfyxckm.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <alpine.LFD.1.10.0806121923400.2949@woody.linux-foundation.org> (Linus Torvalds's message of "Thu, 12 Jun 2008 19:24:18 -0700 (PDT)")

Linus Torvalds <torvalds@linux-foundation.org> writes:

> On Thu, 12 Jun 2008, Jon Loeliger wrote:
>> 
>>     $ git format-patch -1 --stdout --color master
>> 
>> But I seriously doubt that we _really_ want to send a
>> patch that has the embedded escape sequences in it:
>
> Hey, you asked for it, you got it. I hope you're not complaining.

Well, having said and heard all that, coming back to our more serious
selves...

I think being able to do

    $ git -p format-patch --stdout --color -2 HEAD

makes some sense.  Being able to produce an unusable patch by saying

    $ git format-patch --stat old..

at the first glance is of quite dubious value, but even that would make
sense as a good input source for "commit log automailer".

I think I know where Jon is coming from and where he wants to go.  While I
am somewhat sympathetic to the cause of adding some warning or safety
valve to prevent nonsense option combinations from being given, I am not
sure we can draw a line to classify options into black and white.

  reply	other threads:[~2008-06-13  3:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-13  1:14 Dubious format-patch options Jon Loeliger
2008-06-13  2:05 ` Junio C Hamano
2008-06-13  2:24 ` Linus Torvalds
2008-06-13  3:01   ` Junio C Hamano [this message]
2008-06-13  6:33     ` Jeff King

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=7vtzfyxckm.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=jdl@jdl.com \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.