From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH] fetch2: do not try to checksum a socket
Date: Fri, 22 Jun 2012 09:09:36 +0100 [thread overview]
Message-ID: <1340352576.394.6.camel@ted> (raw)
In-Reply-To: <CAC1BbcQgOqcPTnRZksao5yFVH1k8UzcJOCGGO6gzBUWTiPUp7g@mail.gmail.com>
On Thu, 2012-06-21 at 15:57 +0200, Bernhard Reutner-Fischer wrote:
> >
> > FWIW, the url you want is git:///mydir;protocol=file which should work.
>
> Oh, that's rather surprising!
> The format suggested to me that, iff specified, with "protocol=" i can
> select the fetcher, regardless of the actual path-spec.
> Shouldn't protocol have precedence over any eventual path-implied fetcher?
> file:///mydir;protocol=rsync
> rsync -a /mydir S
> file:///mydir;protocol=git
> git clone -s file:///mydir S
No, things work the opposite way around, they always have done and
trying to change that now would be hard. It makes most sense when you
think about it that anything starting with "git://" gets passed to the
git fetcher code, anything "file://" to the local fetcher and so on.
Cheers,
Richard
prev parent reply other threads:[~2012-06-22 8:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-18 11:28 [PATCH] fetch2: do not try to checksum a socket Bernhard Reutner-Fischer
2012-06-21 12:16 ` Richard Purdie
2012-06-21 13:08 ` Bernhard Reutner-Fischer
2012-06-21 13:25 ` Richard Purdie
2012-06-21 13:46 ` Paul Eggleton
2012-06-21 13:57 ` Bernhard Reutner-Fischer
2012-06-22 8:09 ` Richard Purdie [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=1340352576.394.6.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=rep.dot.nop@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