From: Felipe Contreras <felipe.contreras@gmail.com>
To: Johannes Sixt <j.sixt@viscovery.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v2] revision: add --except option
Date: Mon, 2 Sep 2013 01:52:36 -0500 [thread overview]
Message-ID: <CAMP44s0UMb9OOqoLnf219UuH9On0O8hvT5oufSSqO_qnPFb_Mg@mail.gmail.com> (raw)
In-Reply-To: <52243086.6030102@viscovery.net>
On Mon, Sep 2, 2013 at 1:30 AM, Johannes Sixt <j.sixt@viscovery.net> wrote:
> It would be better to settle on the meaning of --except before throwing
> back and forth implementations.
I've lost the count of features that get discussed endlessly, and
nobody implements them ever. The implementation should dictate the
behavior, because it doesn't matter if you have described perfect
behavior, and the implementation is nearly impossible. If you
disagree, feel free to write the code.
Talk is cheap, show me the code. -- Linus Torvalds
--
Felipe Contreras
prev parent reply other threads:[~2013-09-02 6:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-31 21:26 [PATCH v2] revision: add --except option Felipe Contreras
2013-09-02 6:30 ` Johannes Sixt
2013-09-02 6:52 ` Felipe Contreras [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAMP44s0UMb9OOqoLnf219UuH9On0O8hvT5oufSSqO_qnPFb_Mg@mail.gmail.com \
--to=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=j.sixt@viscovery.net \
/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).