From: "Randall S. Becker" <rsbecker@nexbridge.com>
To: "'Jonathan Nieder'" <jrnieder@gmail.com>
Cc: <git@vger.kernel.org>, "'Taylor Blau'" <ttaylorr@github.com>
Subject: RE: [Question] Alternative to git-lfs under go
Date: Mon, 17 Sep 2018 18:38:59 -0400 [thread overview]
Message-ID: <002701d44ed7$3d30f1e0$b792d5a0$@nexbridge.com> (raw)
In-Reply-To: <20180917220209.GJ140909@aiede.svl.corp.google.com>
On September 17, 2018 6:02 PM, Jonathan Nieder wrote:
> Randall S. Becker wrote:
> > 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.
>
> Thanks. Then the answer is "no": there has not been a reimplementation of
> Git LFS in another language, and my advice to someone pursuing that would
> be to use the native Git feature described above instead (or to get Go
> working on their platform).
>
> If I'm reading
> https://github.com/git-lfs/git-lfs/blob/master/CONTRIBUTING.md
> correctly, the preferred way to contact the Git LFS maintainers is using
> Github's issue tracker.
>
> Thanks and sorry I don't have better news, Jonathan
It is the interoperability with existing Git LFS repositories that my community is requesting, not specifically any file size issues. Some want the locking function. The API looks fairly straight forward and I suspect a complete reimplementation will take less of my time than trying to get GO to actually run on the platform. Cross-compilation might be an option, but that's likely a tricky proposition that has not worked in the past - the issue there is that cross compilation requires Windows and Cygwin, which make configure rather confused and so far, not workable. Neither GCC nor GNULIB build completely in port attempts. So the answer is "NO". ☹
prev parent reply other threads:[~2018-09-17 22:39 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
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 [this message]
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='002701d44ed7$3d30f1e0$b792d5a0$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=ttaylorr@github.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).