All of lore.kernel.org
 help / color / mirror / Atom feed
* Upstreaming patches
@ 2011-04-11 23:46 Philip Balister
  2011-04-11 23:59 ` Graham Gower
  0 siblings, 1 reply; 4+ messages in thread
From: Philip Balister @ 2011-04-11 23:46 UTC (permalink / raw)
  To: openembedded-devel

Saul Wold asked me about upstreaming some of the patches in OE. 
Apparently, Intel has some people who can look at submitting some of our 
patches upstream.

The question is, what do we do about attribution? The problem is that is 
not simple for many cases working out who created the patch. Rather than 
spend time chasing through the revision history, it would be simpler to 
send the patches upstream mentioning the source as derived from OE.

My thoughts are no reasonable OE contributor would object to someone 
else upstreaming their patches :), but I thought I should ask people 
what they thought.

Obviously, if there is a complex patch the situation is different, but I 
suspect most of the easy patches do not fall into this category.

Comments?

Philip



^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Upstreaming patches
  2011-04-11 23:46 Upstreaming patches Philip Balister
@ 2011-04-11 23:59 ` Graham Gower
  2011-04-12  7:32   ` Paul Menzel
  2011-04-12  7:34   ` Esben Haabendal
  0 siblings, 2 replies; 4+ messages in thread
From: Graham Gower @ 2011-04-11 23:59 UTC (permalink / raw)
  To: openembedded-devel

On 12 April 2011 09:16, Philip Balister <philip@balister.org> wrote:
> Saul Wold asked me about upstreaming some of the patches in OE. Apparently,
> Intel has some people who can look at submitting some of our patches
> upstream.
>
> The question is, what do we do about attribution? The problem is that is not
> simple for many cases working out who created the patch. Rather than spend
> time chasing through the revision history, it would be simpler to send the
> patches upstream mentioning the source as derived from OE.
>
> My thoughts are no reasonable OE contributor would object to someone else
> upstreaming their patches :), but I thought I should ask people what they
> thought.
>
> Obviously, if there is a complex patch the situation is different, but I
> suspect most of the easy patches do not fall into this category.
>
> Comments?
>
> Philip
>

Sounds good. I think omission of attribution if no original author can
be identified is fine. Its more important that the work not be lost.

Please note that many patches submitted upstream have already been
ignored by upstream.

-Graham



^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Upstreaming patches
  2011-04-11 23:59 ` Graham Gower
@ 2011-04-12  7:32   ` Paul Menzel
  2011-04-12  7:34   ` Esben Haabendal
  1 sibling, 0 replies; 4+ messages in thread
From: Paul Menzel @ 2011-04-12  7:32 UTC (permalink / raw)
  To: openembedded-devel

[-- Attachment #1: Type: text/plain, Size: 1833 bytes --]

Am Dienstag, den 12.04.2011, 09:29 +0930 schrieb Graham Gower:
> On 12 April 2011 09:16, Philip Balister <philip@balister.org> wrote:
> > Saul Wold asked me about upstreaming some of the patches in OE. Apparently,
> > Intel has some people who can look at submitting some of our patches
> > upstream.

That is great. It is indeed very time consuming to find out the correct
place to send patches and register at the ticketing/bug tracking system
or – most of the time – subscribe to the corresponding mailing list.

> > The question is, what do we do about attribution? The problem is that is not
> > simple for many cases working out who created the patch. Rather than spend
> > time chasing through the revision history, it would be simpler to send the
> > patches upstream mentioning the source as derived from OE.
> >
> > My thoughts are no reasonable OE contributor would object to someone else
> > upstreaming their patches :), but I thought I should ask people what they
> > thought.
> >
> > Obviously, if there is a complex patch the situation is different, but I
> > suspect most of the easy patches do not fall into this category.
> >
> > Comments?

> Sounds good. I think omission of attribution if no original author can
> be identified is fine. Its more important that the work not be lost.

In my opinion at least a

        git log --follow recipe/path/to/patch/file.patch

should be tried. Additionally to make things maybe easier it could be
searched for patches with a patch header [1] and track their status.

> Please note that many patches submitted upstream have already been
> ignored by upstream.

Hopefully those patches have a patch header and the report can be
updated easily.


Thanks,

Paul


[1] http://openembedded.org/index.php/Push_patches_upstream

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Upstreaming patches
  2011-04-11 23:59 ` Graham Gower
  2011-04-12  7:32   ` Paul Menzel
@ 2011-04-12  7:34   ` Esben Haabendal
  1 sibling, 0 replies; 4+ messages in thread
From: Esben Haabendal @ 2011-04-12  7:34 UTC (permalink / raw)
  To: openembedded-devel

Graham Gower <graham.gower@gmail.com> writes:

> Sounds good. I think omission of attribution if no original author can
> be identified is fine. Its more important that the work not be lost.
>
> Please note that many patches submitted upstream have already been
> ignored by upstream.

No harm in trying again.

/Esben



^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2011-04-12  7:37 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-04-11 23:46 Upstreaming patches Philip Balister
2011-04-11 23:59 ` Graham Gower
2011-04-12  7:32   ` Paul Menzel
2011-04-12  7:34   ` Esben Haabendal

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.