From: Hauke Mehrtens <hauke@hauke-m.de>
To: "Ozan Çağlayan" <ozancag@gmail.com>
Cc: backports@vger.kernel.org
Subject: Re: Compat-wireless release for 2012-10-24 is baked
Date: Thu, 25 Oct 2012 17:11:21 +0200 [thread overview]
Message-ID: <50895699.6060009@hauke-m.de> (raw)
In-Reply-To: <CAFub=KTgcjeNuL6T3aoV8g3pd4GeQu6QboUeNEMTjcRcq5Ji_w@mail.gmail.com>
On 10/25/2012 04:57 PM, Ozan Çağlayan wrote:
> On Wed, Oct 24, 2012 at 11:14 PM, Compat-wireless cronjob account
> <compat@orbit-lab.org> wrote:
>> git fetch github (/var/opt/compat/compat-wireless-2.6)
>> HEAD is now at a26c7c1 compat-drivers: Enable CONFIG_DRM_LOAD_EDID_FIRMWARE
>> git fetch github (/var/opt/compat/compat)
>> Nothing new to pack.
>> HEAD is now at 8de8ebb compat: encourage non-root use of bin/get-compat-kernels
>> git fetch (/var/opt/compat/linux-next)
>> Nothing new to pack.
>> HEAD is now at d1298f5 Add linux-next specific files for 20121024
>> Error while updating from wireless-testing
>
> Do we have the code of these cron scripts anywhere on the net? Would
> you consider to run bin/get-compat-trees before running this script to
> fetch the latest kernels?
Hi Ozan,
The code of the scripts is here:
https://git.kernel.org/?p=linux/kernel/git/mcgrof/compat-user.git;a=summary
Doesn't get-compat-trees need root rights? If so then I do not think it
is a good idea to run that automatically, but we should test against
some more recent kernels.
Hauke
next prev parent reply other threads:[~2012-10-25 15:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-24 20:14 Compat-wireless release for 2012-10-24 is baked Compat-wireless cronjob account
2012-10-25 14:57 ` Ozan Çağlayan
2012-10-25 15:11 ` Hauke Mehrtens [this message]
2012-10-25 15:20 ` Luis R. Rodriguez
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=50895699.6060009@hauke-m.de \
--to=hauke@hauke-m.de \
--cc=backports@vger.kernel.org \
--cc=ozancag@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.