linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Stezenbach <js@sig21.net>
To: Ivo Van Doorn <ivdoorn@gmail.com>
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>,
	linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Compat-wireless release for 2010-10-25 is baked
Date: Tue, 26 Oct 2010 22:40:43 +0200	[thread overview]
Message-ID: <20101026204043.GA2608@sig21.net> (raw)
In-Reply-To: <AANLkTi=TPCXXki3jrrFA1HiauDp0rZVtMK9fK4z8B_kv@mail.gmail.com>

Hi,

On Tue, Oct 26, 2010 at 09:48:12PM +0200, Ivo Van Doorn wrote:
> For rt2x00 development you can choose between rt2x00.git and
> wireless-testing.git,
> the trees are usually not that far apart, since smaller patches are pushed quite
> quickly upstream. (Also rt2x00.git is rebased frequently, while
> wireless-testing.git rarely
> is rebased)

Thanks for clarification.  I guess I'll start with wireless-testing,
that sounds a bit more newbie-friendly.  I just want to avoid
searching or reporting bugs which are already fixed, but your description
sounds like changes are pushed from rt2x00.git to wireless-testing.git
maybe weekly.  I was afraid patches would be pushed to wireless-testing.git
only when it's time to get ready for the next merge window.


Thanks,
Johannes

  reply	other threads:[~2010-10-26 20:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-25 19:03 Compat-wireless release for 2010-10-25 is baked Compat-wireless cronjob account
2010-10-26 12:35 ` Johannes Stezenbach
2010-10-26 15:59   ` Luis R. Rodriguez
2010-10-26 18:41     ` Johannes Stezenbach
2010-10-26 18:51       ` Luis R. Rodriguez
2010-10-26 19:48         ` Ivo Van Doorn
2010-10-26 20:40           ` Johannes Stezenbach [this message]
2010-10-26 20:52             ` 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=20101026204043.GA2608@sig21.net \
    --to=js@sig21.net \
    --cc=ivdoorn@gmail.com \
    --cc=linux-kernel@vger.kernel.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).