From: "Randall S. Becker" <rsbecker@nexbridge.com>
To: "'Jonathan Nieder'" <jrnieder@gmail.com>
Cc: <git@vger.kernel.org>
Subject: RE: [Question] Alternative to git-lfs under go
Date: Mon, 17 Sep 2018 17:55:55 -0400 [thread overview]
Message-ID: <002501d44ed1$38a49ab0$a9edd010$@nexbridge.com> (raw)
In-Reply-To: <20180917192753.GF140909@aiede.svl.corp.google.com>
On September 17, 2018 3:28 PM, Jonathan Nieder wrote:
> Randall S. Becker wrote:
>
> > Does anyone know whether it is practical to rework git-lfs under a
> > language other than "go"? GCC is not even close to being possible to
> > port to my NonStop platform (may have tried, some have died - joke -
> > trying). I would like to convert this directly to C or something more
> > widely portable. Is there a protocol doc out there I can reference?
>
> Can you say more about the context? You might like
>
> git clone --filter=blob:limit=512m <repo>
>
> which tells Git to avoid downloading any blobs larger than 512 megabytes
> until you know they need them. See Documentation/technical/partial-
> clone.txt
> for more details.
Sorry, I was not clear. I am not having issues with large files or blob
limits. Members of my community wish to use Git LFS support on their
enterprise git servers, so as platform maintainer for git on NonStop, I am
trying to accommodate them. The stumbling block is that "Go" language will
not port to the platform.
Cheers,
Randall
next prev parent reply other threads:[~2018-09-17 21:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-17 19:24 [Question] Alternative to git-lfs under go Randall S. Becker
2018-09-17 19:27 ` Jonathan Nieder
2018-09-17 21:55 ` Randall S. Becker [this message]
2018-09-17 22:00 ` Taylor Blau
2018-09-17 22:23 ` Randall S. Becker
2018-09-17 22:02 ` Jonathan Nieder
2018-09-17 22:38 ` Randall S. Becker
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='002501d44ed1$38a49ab0$a9edd010$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
/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).