From: Dmitry Potapov <dpotapov@gmail.com>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: Abhinav Goyal <honeykool23@gmail.com>, git@vger.kernel.org
Subject: Re: Regarding GIT API
Date: Tue, 15 Feb 2011 20:09:40 +0300 [thread overview]
Message-ID: <AANLkTimtiXN5EpejfCSVERCHhc1F7bKQiRNuf7GxbvaR@mail.gmail.com> (raw)
In-Reply-To: <4D5A744F.5000208@drmicha.warpmail.net>
On Tue, Feb 15, 2011 at 3:40 PM, Michael J Gruber
<git@drmicha.warpmail.net> wrote:
>
> You mean "plumbing" for the commands with robust interface.
>
> The front-end commands are "porcelain": they may break when used for
> heavy (scripting) work...
Thank you for correction...
Dmitry
prev parent reply other threads:[~2011-02-15 17:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-15 11:08 Regarding GIT API Abhinav Goyal
2011-02-15 11:21 ` Erik Faye-Lund
2011-02-15 11:22 ` Marc Weber
2011-02-15 11:49 ` Dmitry Potapov
2011-02-15 12:40 ` Michael J Gruber
2011-02-15 17:09 ` Dmitry Potapov [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=AANLkTimtiXN5EpejfCSVERCHhc1F7bKQiRNuf7GxbvaR@mail.gmail.com \
--to=dpotapov@gmail.com \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=honeykool23@gmail.com \
/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).