From: Alexander Dahl <post@lespocky.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH 2/7] ptxdist: Add local-src command
Date: Fri, 28 Feb 2014 14:48:20 +0100 [thread overview]
Message-ID: <d0a9465f96013d4d7262750cfded8661@idefix.lespocky.dyndns.org> (raw)
In-Reply-To: <1393424001-26060-2-git-send-email-s.hauer@pengutronix.de>
Hei hei,
Am 2014-02-26 15:13, schrieb Sascha Hauer:
> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
> ---
[snip]
> + local-src <pkg> <directory> overwrite a package source with a
> locally provided
> + directory containing the sourcecode.
What exactly is the use case for this? Which source gets overwritten
with what other source and why?
Greets
Alex
--
»With the first link, the chain is forged. The first speech censured,
the first thought forbidden, the first freedom denied, chains us all
irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie)
*** GnuPG-FP: 02C8 A590 7FE5 CA5F 3601 D1D5 8FBA 7744 CC87 10D0 ***
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2014-02-28 13:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 14:13 [ptxdist] [PATCH 1/7] ptxdist: Add list-packages command Sascha Hauer
2014-02-26 14:13 ` [ptxdist] [PATCH 2/7] ptxdist: Add local-src command Sascha Hauer
2014-02-28 13:48 ` Alexander Dahl [this message]
2014-02-28 14:01 ` Sascha Hauer
2014-02-28 14:47 ` Uwe Kleine-König
2014-02-28 14:58 ` Juergen Beisert
2014-02-28 15:54 ` Alexander Dahl
2014-02-26 14:13 ` [ptxdist] [PATCH 3/7] barebox: Add optional dependency to host-libusb Sascha Hauer
2014-02-26 14:13 ` [ptxdist] [PATCH 4/7] barebox: Only install defaultenv file if it exists Sascha Hauer
2014-02-26 14:13 ` [ptxdist] [PATCH 5/7] add ptxsudo alias to ptxdist bash Sascha Hauer
2014-02-26 14:13 ` [ptxdist] [PATCH 6/7] Add dfu-util rules for host Sascha Hauer
2014-02-26 14:13 ` [ptxdist] [PATCH 7/7] dfu-util: version bump to 0.7 Sascha Hauer
2014-02-26 16:30 ` [ptxdist] [PATCH 1/7] ptxdist: Add list-packages command Alexander Dahl
2014-02-27 8:48 ` Sascha Hauer
2014-03-06 17:52 ` Michael Olbrich
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=d0a9465f96013d4d7262750cfded8661@idefix.lespocky.dyndns.org \
--to=post@lespocky.de \
--cc=ptxdist@pengutronix.de \
/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