From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: [ANNOUNCE] tree renaming patches part 1 applied
Date: Tue, 14 Aug 2012 08:59:43 -0300 [thread overview]
Message-ID: <502A3DAF.6080301@redhat.com> (raw)
Yesterday, I finally applied the first part of the renaming patches:
* [RFC,10/10,media] break siano into mmc and usb directories
- http://patchwork.linuxtv.org/patch/11755/
* [RFC,09/10,media] saa7146: Move it to its own directory
- http://patchwork.linuxtv.org/patch/11750/
* [RFC,07/10,media] b2c2: break it into common/pci/usb directories
- http://patchwork.linuxtv.org/patch/11754/
* [RFC,03/10,media] move the dvb/frontends to drivers/media/dvb-frontends
- http://patchwork.linuxtv.org/patch/11752/
* [RFC,05/10,media] dvb-usb: move it to drivers/media/usb/dvb-usb
- http://patchwork.linuxtv.org/patch/11751/
* [RFC,06/10,media] Rename media/dvb as media/pci
- http://patchwork.linuxtv.org/patch/11753/
* [RFC,04/10,media] firewire: move it one level up
- http://patchwork.linuxtv.org/patch/11746/
* [RFC,02/10,media] dvb: move the dvb core one level up
- http://patchwork.linuxtv.org/patch/11747/
* [RFC,08/10,media] common: move media/common/tuners to media/tuners
- http://patchwork.linuxtv.org/patch/11748/
* [RFC,01/10,media] v4l: move v4l2 core into a separate directory
- http://patchwork.linuxtv.org/patch/11749/
As discussed when that patch series got submitted, the target there is to
better organize the drivers, in order to make easier for developers to
know where the things are, and for users to help them to find their
needed drivers.
I'll be working today with the remaining patches to complete the renaming,
as it is better to apply them sooner than later, and we're early at the
development cycle.
Before applying this patch series, I applied almost all pending patches
at the tree, in order to reduce the need for patch changes. I also
reminded on IRC some developers that I was aware that they would be
having pending work.
Anyway, in order to help people that might still have patches against
the old structure, I created a small script and added them at the
media_build tree:
http://git.linuxtv.org/media_build.git/blob/HEAD:/devel_scripts/rename_patch.sh
(in fact, I created an script that auto-generated it ;) )
To use it, all you need to do is:
$ ./rename_patch.sh your_patch
As usual, if you want to change several patches, you could do:
$ git format_patch some_reference_cs
and apply the rename_patch.sh to the generated 0*.patch files, like
$ for i in 0*.patch; do ./rename_patch.sh $i; done
More details about that are at the readme file:
http://git.linuxtv.org/media_build.git/blob/HEAD:/devel_scripts/README
Regards,
Mauro
next reply other threads:[~2012-08-14 11:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-14 11:59 Mauro Carvalho Chehab [this message]
2012-08-14 13:53 ` [ANNOUNCE] tree renaming patches part 1 applied Hans Verkuil
2012-08-14 14:36 ` Mauro Carvalho Chehab
2012-08-16 9:24 ` Sylwester Nawrocki
2012-08-16 10:30 ` Mauro Carvalho Chehab
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=502A3DAF.6080301@redhat.com \
--to=mchehab@redhat.com \
--cc=linux-media@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).