From: Martin Jansa <martin.jansa@gmail.com>
To: Olof Johansson <olof.johansson@axis.com>
Cc: bitbake-devel <bitbake-devel@lists.openembedded.org>
Subject: Re: [PATCH] fetch2/git: Anchor names when using ls-remote
Date: Mon, 20 Jan 2014 17:18:05 +0100 [thread overview]
Message-ID: <20140120161805.GG5565@jama> (raw)
In-Reply-To: <20140120155734.GI6520@axis.com>
[-- Attachment #1: Type: text/plain, Size: 972 bytes --]
On Mon, Jan 20, 2014 at 04:57:34PM +0100, Olof Johansson wrote:
> On 14-01-20 16:21 +0100, Richard Purdie wrote:
> > When specifying tags, they're searched for unanchored so foo/bar could
> > match:
> >
> > refs/heads/abc/foo/bar
> > refs/heads/xyz/foo/bar
> > refs/heads/foo/bar
> >
> > This change anchors the expressions so they are based against heads
> > or tags (or any other base level tree that has been created).
>
> Afaict, ls-remote matches the wildcard character against any
> character, including /.
>
> $ git ls-remote gittest refs/*/foo/bar
> 69ab4bdbb5f3725ca594a2abdb636ee8fc25e1c4 refs/tags/abc/foo/bar
> c8647b027d88af180e90d842577518b73ef6a167 refs/tags/foo/bar
> 149c3c329515086af1ae4e24b12b17100ae16256 refs/tags/xyz/foo/bar
Yes, I've seen the same behavior:
http://lists.openembedded.org/pipermail/bitbake-devel/2013-August/003724.html
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2014-01-20 16:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-20 15:21 [PATCH] fetch2/git: Anchor names when using ls-remote Richard Purdie
2014-01-20 15:57 ` Olof Johansson
2014-01-20 16:18 ` Martin Jansa [this message]
2014-01-20 16:28 ` Richard Purdie
2014-01-20 16:39 ` Martin Jansa
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=20140120161805.GG5565@jama \
--to=martin.jansa@gmail.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=olof.johansson@axis.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