git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] Documentation/git.txt: command re-classification
Date: Fri, 19 Jan 2007 23:18:47 +0100	[thread overview]
Message-ID: <eorg2u$f1o$2@sea.gmane.org> (raw)
In-Reply-To: Pine.LNX.4.64.0701191437450.3011@xanadu.home

Nicolas Pitre wrote:

>> +The interface (input, output, set of options and the semantics)
>> +to these low-level commands are meant to be a lot more stable
>> +than Porcelain level commands, because these commands are
>> +primarily for scripted use.  To put it another way, the
>> +interface to Plumbing commands are subject to change in order to
>> +improve the end user experience.
> 
> I think the "to put it another way" sentence is a bit confusing here.

I think it should read "To put it another way, Porcelain level commands
are subject to change" instead of much less readable "To put it another way,
the interface to Plumbing commands are subject to change".
-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git

  reply	other threads:[~2007-01-19 22:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-18 22:25 [PATCH] Documentation: revisit command qualification in git.txt Nicolas Pitre
2007-01-19  6:32 ` [PATCH] Documentation/git.txt: command re-classification Junio C Hamano
2007-01-19 22:08   ` Nicolas Pitre
2007-01-19 22:18     ` Jakub Narebski [this message]
2007-01-19 22:22     ` Junio C Hamano
2007-01-19 22:44       ` Nicolas Pitre
2007-01-19 22:57         ` Jakub Narebski
2007-01-19 22:59           ` J. Bruce Fields
2007-01-19 23:36         ` Junio C Hamano
2007-01-20  1:44           ` Nicolas Pitre

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='eorg2u$f1o$2@sea.gmane.org' \
    --to=jnareb@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).