All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] support/download/git: Prioritize remote archive
Date: Thu, 18 Aug 2016 11:33:44 +0200	[thread overview]
Message-ID: <20160818093344.GB5930@free.fr> (raw)
In-Reply-To: <CAJsd3zJ_=1YhkD-LWfenYAnzG+4KmqsJ5f-wZFMCUKRbarPhjw@mail.gmail.com>

Benjamin, All,

On 2016-08-18 02:26 -0700, Benjamin Kamath spake thusly:
> On Thu, Aug 18, 2016 at 2:10 AM, Yann E. MORIN <yann.morin.1998@free.fr> wrote:
> > Benjamin, All,
> >
> > On 2016-08-17 15:17 -0700, Benjamin Kamath spake thusly:
> >> On Wed, Aug 17, 2016 at 2:53 PM, Yann E. MORIN <yann.morin.1998@free.fr> wrote:
> >> > Benjmin, All,
> >> >
> >> > On 2016-08-17 14:25 -0700, Benjamin Kamath spake thusly:
> >> >> From: Benjamin Kamath <bkamath@spaceflight.com>
> >> >>
> >> >> Attempt to do a remote archive since it shortcuts us past a few steps when
> >> >> available. Additionally. if the git server has uploadArchive.allowUnreachable
> >> >> set to true, then this method can also work on arbitrary sha1s, offering a huge
> >> >> speed advantage over a full clone.
> >> >
> >> > Do you know of a publicly-accessible server that allows remote archives?
> >> >
> >> > I've tried with a github-hosted package, but githib won;t allow remote
> >> > archives, it seems...
> >> I just tried quite a few and it doesn't seem to be frequently
> >> supported. gitlab-ce does seem to have it enabled by default:
> >>
> >> git at gitlab.com:gitlab-org/gitlab-ce.git
> >
> > OK, it does work, as long as one uses the ssh protocol. It does not work
> > via http:// or git://
> >
> OK. I had not noticed that before, and as such that makes this patch
> much less useful.
> 
> > Which means we have no package in Buildroot that can use this.
> >
> > Do you have a need for that for an internal package?
> Yes, but we can create a local patch for it. On dev-branches of our
> project we frequently have internal packages that point directly at
> sha1s. I mistakenly thought more servers would support remote archive.
> I suppose we should reject this patch.

I'm OK with adding this, as long as it does not break existing
behaviour. From my little tests, it shows that it works.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2016-08-18  9:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-17 21:25 [Buildroot] [PATCH v2] support/download/git: Prioritize remote archive Benjamin Kamath
2016-08-17 21:53 ` Yann E. MORIN
2016-08-17 22:17   ` Benjamin Kamath
2016-08-18  9:10     ` Yann E. MORIN
2016-08-18  9:26       ` Benjamin Kamath
2016-08-18  9:33         ` Yann E. MORIN [this message]
2016-08-18 17:09 ` Yann E. MORIN
2016-08-24 17:47 ` [Buildroot] [PATCH v3] " Benjamin Kamath
2017-02-12 22:01   ` Arnout Vandecappelle

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=20160818093344.GB5930@free.fr \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.