linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Sylwester Nawrocki <s.nawrocki@samsung.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [ANNOUNCE] tree renaming patches part 1 applied
Date: Thu, 16 Aug 2012 07:30:32 -0300	[thread overview]
Message-ID: <502CCBC8.4060504@redhat.com> (raw)
In-Reply-To: <502CBC37.1010800@samsung.com>

Em 16-08-2012 06:24, Sylwester Nawrocki escreveu:
> Hi Mauro,
> 
> On 08/14/2012 01:59 PM, Mauro Carvalho Chehab wrote:
>> 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
> 
> Thanks for preparing this little helper script! It's helpful since I have
> quite a few pending patches, and it also saves time when porting patches
> from older kernel trees.

Anytime!

Anyway, I'm running this script here, when a patch doesn't apply, so, you
don't urge to port patches to the new structure.

Regards,
Mauro

      reply	other threads:[~2012-08-16 10:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-14 11:59 [ANNOUNCE] tree renaming patches part 1 applied Mauro Carvalho Chehab
2012-08-14 13:53 ` 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 [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=502CCBC8.4060504@redhat.com \
    --to=mchehab@redhat.com \
    --cc=linux-media@vger.kernel.org \
    --cc=s.nawrocki@samsung.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).