From: Walter Goldens <goldenstranger@yahoo.com>
To: Hauke Mehrtens <hauke@hauke-m.de>
Cc: linux-wireless@vger.kernel.org, "Luis R. Rodriguez" <mcgrof@gmail.com>
Subject: Re: Compat-wireless release for 2011-04-07 is baked
Date: Thu, 7 Apr 2011 15:08:59 -0700 (PDT) [thread overview]
Message-ID: <895357.54625.qm@web161601.mail.bf1.yahoo.com> (raw)
In-Reply-To: <4D9E30DE.5060500@hauke-m.de>
> >
> > Walter
> Hi Walter,
>
> the subject of this message is wrong, compat-wireless
> release for
> 2011-04-07 was not baked, because some patches do not
> apply. ;-)
> A successful message should look like this:
> http://www.spinics.net/lists/linux-wireless/msg66930.html
> When the statistic is included it was successful.
>
> compat-wireless is build automatically by a daily cron job
> and this cron
> job also sends these mails.
>
> You could apply the patches I send to the mailing list some
> hours ago
> and generate your own compat-wireless version or wait some
> time.
>
> Hauke
Hello Hauke,
I understand the mechanics of the cron job generating compat-wireless tar balls and emails to the mailing list. I don't understand who /or what/ uploads them in kernel.org and orbit lab?
http://www.orbit-lab.org/kernel/compat-wireless-2.6/
http://wireless.kernel.org/download/compat-wireless-2.6/
Walter
PS, I guess this CW bot "baker" needs a little fine-tuning
next prev parent reply other threads:[~2011-04-07 22:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-07 19:04 Compat-wireless release for 2011-04-07 is baked Compat-wireless cronjob account
2011-04-07 20:47 ` Walter Goldens
2011-04-07 21:47 ` Hauke Mehrtens
2011-04-07 22:08 ` Walter Goldens [this message]
2011-04-13 20:25 ` Hauke Mehrtens
2011-04-14 15:32 ` Walter Goldens
2011-04-14 15:38 ` Luis R. Rodriguez
2011-04-15 1:16 ` Luis R. Rodriguez
2011-04-15 13:39 ` Walter Goldens
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=895357.54625.qm@web161601.mail.bf1.yahoo.com \
--to=goldenstranger@yahoo.com \
--cc=hauke@hauke-m.de \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).