public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Antonio Ospite <ospite@studenti.unina.it>
Cc: linux-media@vger.kernel.org, linuxtv-commits@linuxtv.org,
	Drew Fisher <drew.m.fisher@gmail.com>
Subject: Re: [git:v4l-dvb/for_v2.6.40] [media] gspca - kinect: move communications buffers out of stack
Date: Fri, 29 Apr 2011 13:30:01 -0300	[thread overview]
Message-ID: <4DBAE789.5000606@redhat.com> (raw)
In-Reply-To: <20110429181604.df0e6de8.ospite@studenti.unina.it>

Em 29-04-2011 13:16, Antonio Ospite escreveu:
> On Fri, 29 Apr 2011 12:43:55 -0300
> Mauro Carvalho Chehab <mchehab@redhat.com> wrote:
> 
>> Em 29-04-2011 12:27, Antonio Ospite escreveu:
>>> On Fri, 29 Apr 2011 16:42:04 +0200
>>> Mauro Carvalho Chehab <mchehab@redhat.com> wrote:
>>>
>>>> This is an automatic generated email to let you know that the following patch were queued at the 
>>>> http://git.linuxtv.org/media_tree.git tree:
>>>>
>>>> Subject: [media] gspca - kinect: move communications buffers out of stack
>>>> Author:  Antonio Ospite <ospite@studenti.unina.it>
>>>> Date:    Thu Apr 21 06:51:34 2011 -0300
>>>>
>>>
>>> Hi Mauro, actually this one is from Drew Fisher as well, git-am should
>>> have picked up the additional From header:
>>> http://www.spinics.net/lists/linux-media/msg31576.html
>>
>> Gah!
>>
>> Patchwork suffered a crash. Patches got recovered yesterday, but all of them missed
>> the e-mail body:
>> 	https://patchwork.kernel.org/patch/724331/
>>
>> I'm needing to manually edit each patch before applying due to that.
>>
> 
> Just FYI, gmane stores a raw representation of messages which can be
> used with git-am, take:
> http://article.gmane.org/gmane.linux.drivers.video-input-infrastructure/31735
> and add /raw at the end of the URL.

Good to know about the /raw mode of gmane.

I have also my own copy of the patches, but the thing is that the control I use here to know
what patches are still pending is based on patchwork. With pathwork.kernel.org broken,
my legs are also broken :/

After finishing to apply the current stuff there, I intend to think on another process that
won't make me dependent on a software/hardware where I cannot rely on it, nor fix the issues
directly. So, I'm thinking on abandoning the usage of patchwork, but the point is: what other
alternatives are left?

> 
>> I'll revert the patch and re-apply it with the proper authorship.
>>
> 
> Thanks a lot.
> 
> Best regards,
>    Antonio
> 


      reply	other threads:[~2011-04-29 16:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1QFowG-0005SZ-7v@www.linuxtv.org>
2011-04-29 15:27 ` [git:v4l-dvb/for_v2.6.40] [media] gspca - kinect: move communications buffers out of stack Antonio Ospite
2011-04-29 15:43   ` Mauro Carvalho Chehab
2011-04-29 16:16     ` Antonio Ospite
2011-04-29 16: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=4DBAE789.5000606@redhat.com \
    --to=mchehab@redhat.com \
    --cc=drew.m.fisher@gmail.com \
    --cc=linux-media@vger.kernel.org \
    --cc=linuxtv-commits@linuxtv.org \
    --cc=ospite@studenti.unina.it \
    /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