From: Detlev Zundel <dzu@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] What's wrong with this code?
Date: Fri, 26 Mar 2010 11:09:50 +0100 [thread overview]
Message-ID: <m2eij7iec1.fsf@ohwell.denx.de> (raw)
In-Reply-To: <189691269597507@webmail102.yandex.ru> (Dennis Semakin's message of "Fri, 26 Mar 2010 12:58:27 +0300")
Hi Dennis,
> Hi
>>
>> Why don't you wrap this change into a patch and post it here[1] on the
>> mailing list. If there are reasons not to merge it, the respective
>> people will speak up.
>
> Because it's not my patch. I didn't write it. I did only copy and paste.
That's not a big problem. Depending on how correct you want to be, you
could either use "git commit --author <original author>" to commit tha
change into your tree and then use git-send-email to post the patch
here. The git toolchain will correctly keep the authors name even if
you post the patches. Note that patches regularly get (re-)posted by
people not being the original author. As long as it is correct from a
copyright point of view, this is not a problem.
On such a small change however, you may also simply put a short "code
originally by ..." in the commit message.
The _relevant_ part is that people here need a patch to do a proper
review of the change you propose.
Cheers
Detlev
--
You live and learn
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu at denx.de
next prev parent reply other threads:[~2010-03-26 10:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-26 8:40 [U-Boot] What's wrong with this code? Dennis Semakin
2010-03-26 9:30 ` Detlev Zundel
2010-03-26 9:58 ` Dennis Semakin
2010-03-26 10:09 ` Detlev Zundel [this message]
2010-03-26 14:28 ` Dennis Semakin
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=m2eij7iec1.fsf@ohwell.denx.de \
--to=dzu@denx.de \
--cc=u-boot@lists.denx.de \
/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 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.