From: Shawn Pearce <spearce@spearce.org>
To: weigelt@metux.de, "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: GIT as binary repository
Date: Fri, 22 Oct 2010 12:20:17 -0700 [thread overview]
Message-ID: <AANLkTikwWQgnmOK2o8L+vUazHeHR-AqSrcZ4HK4siOA0@mail.gmail.com> (raw)
In-Reply-To: <20101022050257.GB27179@nibiru.local>
On Thu, Oct 21, 2010 at 10:02 PM, Enrico Weigelt <weigelt@metux.de> wrote:
> * Shawn Pearce <spearce@spearce.org> wrote:
> What about splitted blobs ? Is this supported by the object
> format right now ?
Nope.
--
Shawn.
next prev parent reply other threads:[~2010-10-22 19:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-21 12:52 GIT as binary repository Wilson, Kevin Lee (OpenView Engineer)
2010-10-21 14:19 ` Tay Ray Chuan
2010-10-21 19:54 ` Enrico Weigelt
2010-10-21 21:23 ` Shawn Pearce
2010-10-22 5:02 ` Enrico Weigelt
2010-10-22 19:20 ` Shawn Pearce [this message]
2010-10-21 17:38 ` Shawn Pearce
2010-10-21 18:53 ` Wilson, Kevin Lee (OpenView Engineer)
2010-10-21 19:19 ` Enrico Weigelt
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=AANLkTikwWQgnmOK2o8L+vUazHeHR-AqSrcZ4HK4siOA0@mail.gmail.com \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=weigelt@metux.de \
/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).