From: Michael Witten <mfwitten@gmail.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Junio C Hamano <gitster@pobox.com>, Nicolas Pitre <nico@cam.org>,
git@vger.kernel.org
Subject: Re: Compatibility between git.git and jgit
Date: Fri, 1 May 2009 20:40:09 -0500 [thread overview]
Message-ID: <b4087cc50905011840j664710f9xbb377f1578dfab5a@mail.gmail.com> (raw)
In-Reply-To: <20090502000123.GF23604@spearce.org>
On Fri, May 1, 2009 at 19:01, Shawn O. Pearce <spearce@spearce.org> wrote:
>
> But I think in another 12 months we'll be seeing people running
> only JGit in many contexts, making compatibility between the two
> implementations somewhat more important than it has been in the past.
:-D
Getting a little cocky there, eh Shawn?
Interestingly, you don't say "making compatibility **with git.git**
more important"...
Watch your back Junio!
:-D
next prev parent reply other threads:[~2009-05-02 1:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-15 18:27 Weird growth in packfile during initial push Robin H. Johnson
2009-04-15 19:51 ` Nicolas Pitre
2009-04-29 23:57 ` Junio C Hamano
2009-04-30 2:52 ` Nicolas Pitre
2009-05-01 6:17 ` Robin H. Johnson
2009-05-01 20:56 ` [PATCH] allow OFS_DELTA objects during a push Nicolas Pitre
2009-05-01 23:49 ` Junio C Hamano
2009-05-02 0:01 ` Compatibility between git.git and jgit Shawn O. Pearce
2009-05-02 1:14 ` A Large Angry SCM
2009-05-02 1:39 ` Nicolas Pitre
2009-05-02 1:59 ` Shawn O. Pearce
2009-05-02 16:56 ` Ealdwulf Wuffinga
2009-05-02 1:40 ` Michael Witten [this message]
2009-05-02 0:24 ` [PATCH] allow OFS_DELTA objects during a push Nicolas Pitre
2009-05-04 22:11 ` Shawn O. Pearce
2009-05-04 22:30 ` Shawn O. Pearce
-- strict thread matches above, loose matches on Subject: below --
2009-05-02 11:00 Compatibility between git.git and jgit Mark Struberg
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=b4087cc50905011840j664710f9xbb377f1578dfab5a@mail.gmail.com \
--to=mfwitten@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=nico@cam.org \
--cc=spearce@spearce.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).