From: Junio C Hamano <gitster@pobox.com>
To: David Barr <davidbarr@google.com>
Cc: GIT Mailing-list <git@vger.kernel.org>
Subject: Re: [RFC/PATCH 1/3] protobuf: minimal implementation for compact in-memory structures
Date: Fri, 24 Jun 2011 09:48:11 -0700 [thread overview]
Message-ID: <7vei2j18hg.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <BANLkTim3WeCHp=ECDBcbHjT=Guv_epL90Q@mail.gmail.com> (David Barr's message of "Fri, 24 Jun 2011 09:04:11 -0700")
David Barr <davidbarr@google.com> writes:
>> How does this relate to http://code.google.com/p/protobuf/ which has a
>> very similar name? If we do not intend to have any interoperability with
>> it, we should avoid such a confusing name, I think.
>
> The relationship is that the design is shamelessly copied.
... and this will be API and bytestream compatible with that other
protobuf?
If not, please don't use that name. It confuses people, and if somebody
wants to take libified part of our codebase into their application and
link with the real protobuf, it will get even more confusing ;-).
You can (and should) still state that the design was inspired by the other
work in the comment at the beginning of the file or something.
Thanks.
next prev parent reply other threads:[~2011-06-24 16:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-22 7:33 [RFC/PATCH 0/3] David Barr
2011-06-22 7:33 ` [RFC/PATCH 1/3] protobuf: minimal implementation for compact in-memory structures David Barr
2011-06-22 19:42 ` Junio C Hamano
2011-06-24 14:39 ` David Barr
2011-06-24 16:04 ` David Barr
2011-06-24 16:48 ` Junio C Hamano [this message]
2011-06-23 17:22 ` Junio C Hamano
2011-06-22 7:33 ` [RFC/PATCH 2/3] small-alloc: add allocator for small objects David Barr
2011-06-22 20:49 ` Junio C Hamano
2011-06-24 14:38 ` David Barr
2011-06-24 17:02 ` David Barr
2011-06-23 17:17 ` Junio C Hamano
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=7vei2j18hg.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=davidbarr@google.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).