From: Esben Haabendal <eha@dev.doredevelopment.dk>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Upstreaming patches
Date: Tue, 12 Apr 2011 09:34:53 +0200 [thread overview]
Message-ID: <87r597ylb6.fsf@eha.doredevelopment.dk> (raw)
In-Reply-To: <BANLkTimGgmPt2sp69FmDZutgOZoEqwsQzA@mail.gmail.com> (Graham Gower's message of "Tue, 12 Apr 2011 09:29:52 +0930")
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
prev parent reply other threads:[~2011-04-12 7:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
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 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=87r597ylb6.fsf@eha.doredevelopment.dk \
--to=eha@dev.doredevelopment.dk \
--cc=openembedded-devel@lists.openembedded.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