linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: linux-wireless@vger.kernel.org, linux-bluetooth@vger.kernel.org
Cc: Hauke Mehrtens <hauke@hauke-m.de>
Subject: Re: Compat-wireless release for 2010-06-15v2 is baked
Date: Tue, 15 Jun 2010 18:17:32 -0700	[thread overview]
Message-ID: <AANLkTikR8XOdDocNAyTtezjgjpctRCteg5Q-W97cHiyP@mail.gmail.com> (raw)
In-Reply-To: <AANLkTik49vfTI7UHzCOGJRXdAYJN9fLmwS-xNcHeBcAu@mail.gmail.com>

On Tue, Jun 15, 2010 at 5:41 PM, Luis R. Rodriguez <mcgrof@gmail.com> wrote:
> Ok if you don't see any more of these daily please kick me or Haukes.
> Both of us should have access to fix pushing these out now from orbit.
> The backup in case orbit goes down is:
>
> http://wireless.kernel.org/download/compat-wireless-2.6/

Here's another idea. If I'm on vacation or whatever, those who have
access to orbit could just flip a switch and change the git URL to
point to some other git tree to be used as base. Then to aid companies
who want to set up their own repository in case they need more timely
mannered releases based on pending patches you can use this:

git://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/compat-user.git

This is the same setup as what we have at orbit, it mimics the user
environment at Orbit, so all you need is an account and space and to
set up a cronjob (read the README). If you find bugs/enhancement to
the scripts just post 'em too.

For those that can wait on me I guess Orbit will do :)

  Luis

      reply	other threads:[~2010-06-16  1:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-16  0:38 Compat-wireless release for 2010-06-15v2 is baked Compat-wireless cronjob account
2010-06-16  0:41 ` Luis R. Rodriguez
2010-06-16  1:17   ` Luis R. Rodriguez [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=AANLkTikR8XOdDocNAyTtezjgjpctRCteg5Q-W97cHiyP@mail.gmail.com \
    --to=mcgrof@gmail.com \
    --cc=hauke@hauke-m.de \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    /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).