From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/dvb-apps: fix downloading
Date: Tue, 01 Jan 2013 15:36:45 +0100 [thread overview]
Message-ID: <87sj6lrmv6.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1356954095-21337-1-git-send-email-yann.morin.1998@free.fr> (Yann E. MORIN's message of "Mon, 31 Dec 2012 12:41:35 +0100")
>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
Yann> As we're using the sources from the Mercurial repository, and Buildroot
Yann> does support retrieving from a Mercurial repository, there is no need
Yann> to try (and fail1) getting the archive from the Mercurial built-in
Yann> tarball mechanism.
Yann> (Note: I was beaten by this because I had a cached copy locally, left
Yann> after the previous tvheadend-vampirises-files-from-toher-packages attempt,
Yann> that I forgot to delete before testing. Ouch...)
Committed, thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2013-01-01 14:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-31 11:41 [Buildroot] [PATCH] package/dvb-apps: fix downloading Yann E. MORIN
2013-01-01 14:36 ` Peter Korsgaard [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=87sj6lrmv6.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox