From: Pavel Roskin <proski@gnu.org>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Compat-wireless release for 2010-06-30 is baked
Date: Wed, 30 Jun 2010 15:27:47 -0400 [thread overview]
Message-ID: <1277926067.6591.3.camel@mj> (raw)
In-Reply-To: <20100630190300.056B742E2B@repository3.orbit-lab.org>
On Wed, 2010-06-30 at 15:02 -0400, Compat-wireless cronjob account
wrote:
> From git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next
> 4570588..85e0e99 history -> origin/history
> + 1b72384...7a6353a master -> origin/master (forced update)
> 5904b3b..984bc96 stable -> origin/stable
> * [new tag] next-20100630 -> next-20100630
> cat: /var/opt/compat/compat-wireless-2.6/compat_version: No such file or directory
> cat: compat_base_tree: No such file or directory
Luis, could you please check what is going on? There was another
announcement with error messages. Then there was a truncated message.
Now the errors are back.
I'm not sure such messages should be posted to the list. It would be
more useful to send then to those who can do something in the build
system breaks.
--
Regards,
Pavel Roskin
prev parent reply other threads:[~2010-06-30 19:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-30 19:02 Compat-wireless release for 2010-06-30 is baked Compat-wireless cronjob account
2010-06-30 19:27 ` Pavel Roskin [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=1277926067.6591.3.camel@mj \
--to=proski@gnu.org \
--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).