On Mon, Jan 16, 2017 at 12:40 PM, Jonathan Yu wrote:
> What about git-annex? https://apps.fedoraproject.org/packages/git-annex
>
Unfortunately, we don't manage what our clients are using. LFS is now
supported directly in Github, Gitlab, and Bitbucket (and probably others),
We would probably need help getting git-lfs packaged first. That's really
the biggest blocker to enabling it by default.
On Jan 16, 2017, at 9:40 AM, Philippe Lafoucrière <
philippe.lafoucri...@tech-angels.com> wrote:
@Clayton, does it sound reasonable to you to ask for LFS support in s2i?
If
@Clayton, does it sound reasonable to you to ask for LFS support in s2i?
If yes, where should this ticket go?
https://github.com/openshift/source-to-image ?
Thanks
___
users mailing list
users@lists.openshift.redhat.com
On Thu, Jan 12, 2017 at 8:36 PM, Clayton Coleman
wrote:
> Is git-lfs packaged in epel ben?
>
does not appear to be, no. There is a rhel package, but it's not produced
by us:
https://github.com/git-lfs/git-lfs/wiki/Installation#rhelcentos
>
> On Jan 12, 2017, at 4:10
Is git-lfs packaged in epel ben?
On Jan 12, 2017, at 4:10 PM, Philippe Lafoucrière <
philippe.lafoucri...@tech-angels.com> wrote:
On Thu, Jan 12, 2017 at 3:54 PM, Ben Parees wrote:
> that qualifies as client-side logic (the plugin is executing the logic on
> the client
On Thu, Jan 12, 2017 at 3:52 PM, Philippe Lafoucrière <
philippe.lafoucri...@tech-angels.com> wrote:
>
> On Thu, Jan 12, 2017 at 3:50 PM, Ben Parees wrote:
>
>> it's part of the origin/sti-builder infrastructure image. if git-lfs
>> requires client side logic, it's not
On Thu, Jan 12, 2017 at 3:50 PM, Ben Parees wrote:
> it's part of the origin/sti-builder infrastructure image. if git-lfs
> requires client side logic, it's not going to work with openshift s2i
> builds i'm afraid. (at least not w/o some hackery like doing the git clone
>
On Thu, Jan 12, 2017 at 3:47 PM, Philippe Lafoucrière <
philippe.lafoucri...@tech-angels.com> wrote:
>
> On Thu, Jan 12, 2017 at 3:43 PM, Ben Parees wrote:
>
>> no known issues but no known uses either. s2i is basically just git
>> cloning your repo, it sounds like the lfs
On Thu, Jan 12, 2017 at 3:43 PM, Ben Parees wrote:
> no known issues but no known uses either. s2i is basically just git
> cloning your repo, it sounds like the lfs pointers didn't resolve properly
> during the clone operation. I don't know the inner workings of how that
n 12 19:58 admin.war
>
> The content of the files (instead of the actual file):
>
> version https://git-lfs.github.com/spec/v1
> oid sha256:
> 880acdc04e3bc0c9ef2593042360012419d05bb910a9053da1607719cb6b1adc
> size 10332227
>
>
10 matches
Mail list logo