From: Sverre Rabbelier <srabbelier@gmail.com>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: git@vger.kernel.org
Subject: Re: APIs for automatic patch generation
Date: Tue, 23 Feb 2010 19:07:10 +0100 [thread overview]
Message-ID: <fabb9a1e1002231007p650d78fere904f6e5572b12d@mail.gmail.com> (raw)
In-Reply-To: <4B840EF5.2090306@web.de>
Heya,
On Tue, Feb 23, 2010 at 18:23, Markus Elfring <Markus.Elfring@web.de> wrote:
> I do not need the whole functionality of these commands for my library.
My answer still holds.
--
Cheers,
Sverre Rabbelier
next prev parent reply other threads:[~2010-02-23 18:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-20 19:40 APIs for automatic patch generation Markus Elfring
2010-02-23 17:04 ` Markus Elfring
2010-02-23 17:07 ` Sverre Rabbelier
2010-02-23 17:23 ` Markus Elfring
2010-02-23 18:07 ` Sverre Rabbelier [this message]
2010-12-13 16:00 ` Markus Elfring
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=fabb9a1e1002231007p650d78fere904f6e5572b12d@mail.gmail.com \
--to=srabbelier@gmail.com \
--cc=Markus.Elfring@web.de \
--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).