git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Christian Couder <christian.couder@gmail.com>
Cc: Christian Couder <chriscool@tuxfamily.org>, git <git@vger.kernel.org>
Subject: Re: On "interpret-trailers" standalone tool
Date: Wed, 16 Apr 2014 11:40:34 -0700	[thread overview]
Message-ID: <xmqqlhv5glst.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <xmqq38hdi2zr.fsf@gitster.dls.corp.google.com> (Junio C. Hamano's message of "Wed, 16 Apr 2014 10:43:52 -0700")

Junio C Hamano <gitster@pobox.com> writes:

> ...  I am looking at this
> more from the angle of obtaining a useful building block, while you
> seem to be thinking of this as a specialized tool for a narrow set
> of specifkc tasks.

By the way, I am speaking with a bitter experience of designing the
original "format-patch" command line parameters, thinking that "This
is a specialized tool to let me send what Linus hasn't picked up
yet, so the command should take where Linus is and where I am".

Not using the A..B syntax turned out to be a poor choice but that
realization came long after the ship sailed---back then, A..B syntax
was relatively new and it was unclear that it would become the
universal syntax we use throughout the system to denote a range of
commits in the DAG.

The design mistake for starting at a specialized tool for a narrow
set of specific tasks took considerable effort to retrofit the
general syntax while not breaking the traditional usage.  I am being
cautious here because I do not see us making the same mistake.

  reply	other threads:[~2014-04-16 18:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-09 19:57 On "interpret-trailers" standalone tool Junio C Hamano
2014-04-12 19:30 ` Christian Couder
2014-04-14 21:41   ` Junio C Hamano
2014-04-16 12:27     ` Christian Couder
2014-04-16 17:43       ` Junio C Hamano
2014-04-16 18:40         ` Junio C Hamano [this message]
2014-04-16 18:54           ` Junio C Hamano

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=xmqqlhv5glst.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox.com \
    --cc=chriscool@tuxfamily.org \
    --cc=christian.couder@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).