public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Graeme Russ <graeme.russ@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] u-boot sparc for leon3-altera-ep2s60-sdr working
Date: Sat, 12 Feb 2011 20:33:05 +1100	[thread overview]
Message-ID: <4D5653D1.5070303@gmail.com> (raw)
In-Reply-To: <201102121023.06247.fabio.giovagnini@aurion-tech.com>

On 12/02/11 20:23, Fabio Giovagnini wrote:
> On Saturday 12 February 2011 08:13:08 Albert ARIBAUD wrote:
>> Hi Fabio,
>>
>> Le 11/02/2011 14:45, Fabio Giovagnini a ?crit :
>>> Hi guys, I'd like to add the configuration for leon3-altera-ep2s60-sdr
>>> board. What could be the best working way to have an automatic patch
>>> generator?
>>
>> Make one, I guess. :)
>>
>> Seriously, though: what do you mean by "automatic patch generator"?
>>
>> If you mean "I've done modifications to the official U-boot source code
>> and now I need to create a diff patch between my curent source tree and
>> the official U-boot source tree", then that's what git is for.
> Exactly this.
> I started to study git, so I'm doing some tests.
> 

git format-patch is your friend :)

I would recommend stg (stacked git) - It will allow you to mess around with
(and mess up) patches without polluting your git tree

It is really just a wrapper around git commands, but for me, it makes like
a lot easier

> Thanks
> Cheers
> 
>>
>> If you mean something else, please explain.
>>
>>> Thanks
>>>
>>> Fabio Giovagnini
>>
>> Amicalement,
> 

Regards,

Graeme

  reply	other threads:[~2011-02-12  9:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-11 13:45 [U-Boot] u-boot sparc for leon3-altera-ep2s60-sdr working Fabio Giovagnini
2011-02-12  7:13 ` Albert ARIBAUD
2011-02-12  9:23   ` Fabio Giovagnini
2011-02-12  9:33     ` Graeme Russ [this message]
2011-02-12  9:35       ` Fabio Giovagnini
2011-02-12  9:40       ` 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=4D5653D1.5070303@gmail.com \
    --to=graeme.russ@gmail.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