All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Christian Couder <chriscool@tuxfamily.org>
Cc: christian.couder@gmail.com, git@vger.kernel.org,
	johan@herland.net, josh@joshtriplett.org, tr@thomasrast.ch,
	mhagger@alum.mit.edu, sunshine@sunshineco.com,
	dan.carpenter@oracle.com, greg@kroah.com, peff@peff.net
Subject: Re: [PATCH v5 02/14] trailer: process trailers from file and arguments
Date: Fri, 14 Feb 2014 15:57:31 -0800	[thread overview]
Message-ID: <xmqqtxc1fdsk.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20140214.224133.484636406629780362.chriscool@tuxfamily.org> (Christian Couder's message of "Fri, 14 Feb 2014 22:41:33 +0100 (CET)")

Christian Couder <chriscool@tuxfamily.org> writes:

> but we also want to say:
>
>     action = do_Y_if_X_and_Z AND do_U_if_V
>
> For example some people might want:
>
>     if_exists = overwrite
>     if_missing = add
>
> while others might want:
>
>     if_exists = overwrite
>     if_missing = do_nothing
>
> and I don't see how we can say that with just:
>
>     action = do_Y_if_X_and_Z

That is a very relevant illustration that makes me realize why I
found your "if-exists/if-missing = do-Y-if-Z" somewhat distasteful.

Your

     if_exists = add_if_different

says "if the same key is there, add it if the value is different",
but it also implicitly says "donothing if the value is the same".

That is, you are saying with the above

     if_exists = add_if_different AND ignore_if_same

So you already have to support more than one actions depending on
the condition, unless you want to limit the actions for all the
cases other than X to be only "ignore" when you invent your next
"do_Y_if_X", X being "different" in this case, but you support (and
need to support) "different-neighbour" and other random collections
of conditions, I think.  Which is essentially the same as saying
that you need this:

>     action = do_Y_if_X_and_Z AND do_U_if_V

Again, unless all the U's are limited to "ignore", that is.

  parent reply	other threads:[~2014-02-14 23:57 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-06 20:19 [PATCH v5 00/14] Add interpret-trailers builtin Christian Couder
2014-02-06 20:19 ` [PATCH v5 01/14] Add data structures and basic functions for commit trailers Christian Couder
2014-02-06 23:44   ` Junio C Hamano
2014-02-09 13:48     ` Christian Couder
2014-02-10  7:27       ` Eric Sunshine
2014-02-06 23:46   ` Junio C Hamano
2014-02-09 13:51     ` Christian Couder
2014-02-06 20:19 ` [PATCH v5 02/14] trailer: process trailers from file and arguments Christian Couder
2014-02-07  0:03   ` Junio C Hamano
2014-02-09 13:52     ` Christian Couder
2014-02-10 18:14       ` Junio C Hamano
2014-02-10 19:59         ` Christian Couder
2014-02-10 20:51           ` Junio C Hamano
2014-02-11 15:02             ` Christian Couder
2014-02-11 18:07               ` Junio C Hamano
2014-02-14 21:41                 ` Christian Couder
2014-02-14 21:46                   ` Junio C Hamano
2014-02-14 23:29                     ` Christian Couder
2014-02-14 23:39                       ` Junio C Hamano
2014-02-14 23:57                   ` Junio C Hamano [this message]
2014-02-15  0:16                     ` Junio C Hamano
2014-02-21  0:22                       ` Junio C Hamano
2014-02-23 10:44                         ` Christian Couder
2014-02-06 20:19 ` [PATCH v5 03/14] trailer: read and process config information Christian Couder
2014-02-06 20:19 ` [PATCH v5 04/14] trailer: process command line trailer arguments Christian Couder
2014-02-07  0:08   ` Junio C Hamano
2014-02-09 14:06     ` Christian Couder
2014-02-06 20:19 ` [PATCH v5 05/14] trailer: parse trailers from input file Christian Couder
2014-02-06 20:19 ` [PATCH v5 06/14] trailer: put all the processing together and print Christian Couder
2014-02-06 20:19 ` [PATCH v5 07/14] trailer: add interpret-trailers command Christian Couder
2014-02-07  0:10   ` Junio C Hamano
2014-02-07  8:34     ` Christian Couder
2014-02-07 18:09       ` Junio C Hamano
2014-02-07 20:35         ` Junio C Hamano
2014-02-06 20:19 ` [PATCH v5 08/14] trailer: add tests for "git interpret-trailers" Christian Couder
2014-02-07  0:11   ` Junio C Hamano
2014-02-06 20:19 ` [PATCH v5 09/14] trailer: if no input file is passed, read from stdin Christian Couder
2014-02-07  0:12   ` Junio C Hamano
2014-02-06 20:19 ` [PATCH v5 10/14] trailer: execute command from 'trailer.<name>.command' Christian Couder
2014-02-07  0:18   ` Junio C Hamano
2014-02-07 18:17   ` Junio C Hamano
2014-02-06 20:20 ` [PATCH v5 11/14] trailer: add tests for trailer command Christian Couder
2014-02-06 20:20 ` [PATCH v5 12/14] trailer: set author and committer env variables Christian Couder
2014-02-07  0:20   ` Junio C Hamano
2014-02-07  0:26   ` Junio C Hamano
2014-02-06 20:20 ` [PATCH v5 13/14] trailer: add tests for commands using " Christian Couder
2014-02-06 20:20 ` [PATCH v5 14/14] Documentation: add documentation for 'git interpret-trailers' Christian Couder
2014-02-10  7:17   ` Eric Sunshine

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=xmqqtxc1fdsk.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox.com \
    --cc=chriscool@tuxfamily.org \
    --cc=christian.couder@gmail.com \
    --cc=dan.carpenter@oracle.com \
    --cc=git@vger.kernel.org \
    --cc=greg@kroah.com \
    --cc=johan@herland.net \
    --cc=josh@joshtriplett.org \
    --cc=mhagger@alum.mit.edu \
    --cc=peff@peff.net \
    --cc=sunshine@sunshineco.com \
    --cc=tr@thomasrast.ch \
    /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.