All of lore.kernel.org
 help / color / mirror / Atom feed
* compat-wireless branch for wireless-testing, "wl"
@ 2010-06-02  2:20 Luis R. Rodriguez
  0 siblings, 0 replies; only message in thread
From: Luis R. Rodriguez @ 2010-06-02  2:20 UTC (permalink / raw)
  To: linux-wireless, linux-bluetooth; +Cc: Senthil Balasubramanian, Felix Fietkau

Some developers or users may not have linux-next.git or the
linux-2.6-allstable.git trees around and only keep a local
wireless-testing.git tree around. For those there is a branch now on
compat-wireless called "wl" (I got it from the localversion-wireless
file) which you can use to generate tarballs based on only the latest
wireless-testing updates. I've kept the pending and crap patches on it
for now but those will likely be removed once John starts merging
stuff back in.

I would prefer if people who do contribute on compat-wireless work
more on the master branch of compat-wireless and linux-next.git
instead though as this allows us to start backporting the next kernel
release headaches early on and not at cram time during or right after
the merge window. The "wl" branch is there to aid developers who do
not have the linux-next.git tree around or for Linux distributions who
currently may not care about updates on the kernel development cycle
on the other subsystems since wireless-testing only gets only 802.11
updates. An example is openwrt which uses only wireless-testing.git.

If you send me patches I will assume they are for the master branch of
compat-wireless unless otherwise specified. I will try to keep it the
wireless-testing branch updated but patches for it are always
welcomed. I will try to follow the upstream model though so would
first want the patches on the master branch of compat-wireless and
only then trickle them down for the "wl" branch. Since there is a time
delay between patches getting in wireless-next.git and linux-next.git
there may be an inherent delay between propagating patches down to the
"wl" branch. Not sure, we'll see. If you have a better idea of how to
handle this please let me know.

  Luis

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2010-06-02  2:20 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-06-02  2:20 compat-wireless branch for wireless-testing, "wl" Luis R. Rodriguez

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.