From: Vovk Konstantin <ksl@kslemb.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-Boot-v2009.01-rc2 w90p710 ARM support PATCH
Date: Mon, 19 Jan 2009 13:44:36 +0200 [thread overview]
Message-ID: <003e01c97a2b$516e8630$0201a8c0@main> (raw)
In-Reply-To: 20090117100932.GA32614@game.jcrosoft.org
Maybe is the stupid queston.
How I can do it?
My sequence is:
1. I correct all w90p710 sources for respect to U-Boot coding style.
2. Next I clone U-Boot repository with git clone command
3. Create the new branch w90p710 with git branch command
4. Checkout to the new branch
5. Add corrected sources to the new branch with git add command
6. Commit this changes with git commit -a command
7. Next I create the patch betwen two branches with git diff master w90p710
What I do in the next step:
Post the patch on the mail list or pull my brunch to the server with git
pull origin w90p710:w90p710
Sorry for inconvenience...
Best regards,
Konstantin Vovk.
----- Original Message -----
From: "Jean-Christophe PLAGNIOL-VILLARD" <plagnioj@jcrosoft.com>
To: "Vovk Konstantin" <ksl@kslemb.com>
Cc: <u-boot@lists.denx.de>
Sent: Saturday, January 17, 2009 12:09 PM
Subject: Re: [U-Boot] U-Boot-v2009.01-rc2 w90p710 ARM support PATCH
> On 18:52 Fri 16 Jan , Vovk Konstantin wrote:
>> This patch will add W90P710 ARM7 SoC to u-boot-v2009-rc2.
>>
>> Best regards
>> Konstantin Vovk
>> KSL Embdedded Ltd
>> www.kslemb.com
>>
>> w90p710-v2009.01-rc2.diff:
>> Size: 92K
> please generate a correct patch
> with commit message and Signed-off-by
> and try to use git to generate the patch
> please also note your patch is corrupter by your mailer
> and your patch does not respect our coding style as tab for indenting
> etc...
>
> Best Regards,
> J.
>
next prev parent reply other threads:[~2009-01-19 11:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-16 16:52 [U-Boot] U-Boot-v2009.01-rc2 w90p710 ARM support PATCH Vovk Konstantin
2009-01-17 10:09 ` Jean-Christophe PLAGNIOL-VILLARD
2009-01-19 11:44 ` Vovk Konstantin [this message]
2009-01-19 19:25 ` Wolfgang Denk
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='003e01c97a2b$516e8630$0201a8c0@main' \
--to=ksl@kslemb.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox