From: Vipin KUMAR <vipin.kumar@st.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Question about patches
Date: Tue, 20 Jul 2010 14:36:11 +0530 [thread overview]
Message-ID: <4C456703.10502@st.com> (raw)
In-Reply-To: <201007200939.36563.fabio.giovagnini@aurion-tech.com>
On 7/20/2010 1:09 PM, Fabio Giovagnini wrote:
> Hi Vipin,
> I'm not so smart in diff / patch and git tools usage.
> Could be so kind to write to me how to build a patch for just one file I have
> modified in driver/mtd directory of u-boot?
>
> Thanks in advange and sorry for my request, but I read on the net and nothing
> appeared to be usfull.
>
No problems. It takes a little time to get used to git but then you start liking
it. Anyway
you can create a patch for each commit. You can see a summary of commits via
"git log"
Basically you need to run git format-patch -n <reference>
reference is a branch name or tag or a direct reference to commit from which
you want to create patches
eg git format-patch -n origin/master would create numbered patches for commits
after the commit pointed to by origin/master
Also, run "gitk --all -1000" to get an understanding of what exactly is
happening in the background when you commit a change
Hope this helps a little
Vipin
> Thanks and sorry again
>
>
> In data marted? 20 luglio 2010 09:00:39, Vipin KUMAR ha scritto:
> : > On 7/20/2010 12:25 PM, Fabio Giovagnini wrote:
>>> Hi all,
>>> for sending a patch do I need to have on my PC two u-bbot tree, one
>>> original obtaned by git command, and another to make the modifications?
>>>
>>> Or can I produce the patches using the original tree resident on git
>>> server?
>>
>> Ciao Fabio,
>>
>> You can use git format patch command to produce numbered patches
>> You can google it to know more
>>
>> Regards
>> Vipin
>>
>>> Thanks
>>
>
next prev parent reply other threads:[~2010-07-20 9:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-20 6:55 [U-Boot] Question about patches Fabio Giovagnini
2010-07-20 7:00 ` Vipin KUMAR
2010-07-20 7:39 ` Fabio Giovagnini
2010-07-20 7:52 ` Xiangfu Liu
2010-07-20 8:09 ` Fabio Giovagnini
2010-07-20 9:06 ` Vipin KUMAR [this message]
2010-07-20 9:21 ` Graeme Russ
2010-07-20 9:52 ` Wolfgang Denk
2010-07-20 10:00 ` Reinhard Meyer
2010-07-20 11:35 ` Graeme Russ
2010-07-20 12:59 ` Wolfgang Denk
2010-07-20 15:29 ` Xiangfu Liu
2010-07-20 23:22 ` Graeme Russ
2010-07-20 7:50 ` Stefano Babic
2010-07-20 9:46 ` 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=4C456703.10502@st.com \
--to=vipin.kumar@st.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