From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: Dropping Git.pm (at least Git.xs)?
Date: Mon, 11 Sep 2006 10:58:20 +0200 [thread overview]
Message-ID: <ee38f8$pp8$1@sea.gmane.org> (raw)
In-Reply-To: 20060911032557.GF23891@pasky.or.cz
Petr Baudis wrote:
> Dear diary, on Mon, Sep 11, 2006 at 12:13:01AM CEST, I got a letter
> where Jakub Narebski <jnareb@gmail.com> said that...
>> Could you please put appropriate information on GitWiki
>> http://git.or.cz/gitwiki/InterfacesFrontendsAndTools
>> Perhaps it would be good time to start new section, Git Implementations,
>> and put egit (Java GIT library and Eclipse plugin) there too.
>
> This really isn't a Git reimplementation (thankfully).
Perhaps "language binding" would be better name...
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2006-09-11 8:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-03 11:34 Dropping Git.pm (at least Git.xs)? Junio C Hamano
2006-09-03 15:03 ` Dennis Stosberg
2006-09-10 17:59 ` Sam Vilain
2006-09-10 22:13 ` Jakub Narebski
2006-09-11 3:25 ` Petr Baudis
2006-09-11 8:58 ` Jakub Narebski [this message]
2006-09-07 19:51 ` Petr Baudis
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='ee38f8$pp8$1@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).