From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] git: add SRC_URI name
Date: Mon, 22 Feb 2010 23:45:43 +0100 [thread overview]
Message-ID: <20100222224543.GD30265@mx.loc> (raw)
In-Reply-To: <20100222220621.GB27420@denix.org>
On Mon, Feb 22, 2010 at 05:06:21PM -0500, Denys Dmytriyenko wrote:
>> Not using "archive" as Martin likes as default, but uri%d, but
>
>For multiple SRC_URIs, using uri1/uri2 can be more confusing and may be not
>much better than looking up real names in .inc file...
ok, so let's drop that superfluous .note and the url%d handling.
Other opinions?
next prev parent reply other threads:[~2010-02-22 22:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-21 15:32 [PATCH] git: add SRC_URI name Bernhard Reutner-Fischer
2010-02-22 16:24 ` Denys Dmytriyenko
2010-02-22 16:55 ` Phil Blundell
2010-02-22 17:06 ` Chris Larson
2010-02-22 18:17 ` Martin Jansa
2010-02-22 19:41 ` Bernhard Reutner-Fischer
2010-02-22 21:43 ` Bernhard Reutner-Fischer
2010-02-22 22:06 ` Denys Dmytriyenko
2010-02-22 22:45 ` Bernhard Reutner-Fischer [this message]
2010-02-24 17:18 ` Bernhard Reutner-Fischer
2010-03-05 20:53 ` Bernhard Reutner-Fischer
2010-03-22 11:07 ` Roman Khimov
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=20100222224543.GD30265@mx.loc \
--to=rep.dot.nop@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
/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