From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] Fix AMCC bootstrap option letter label order
Date: Wed, 25 Apr 2007 16:14:41 +0200 [thread overview]
Message-ID: <200704251614.41535.sr@denx.de> (raw)
In-Reply-To: <1628E43D99629C46988BE46087A3FBB997ADFB@ep-01.EmbeddedPlanet.local>
Hi Jeff,
On Wednesday 25 April 2007 15:52, Jeff Mann wrote:
> > It happened earlier too, that you change the file modes.
> > Please make sure that future patches do not touch the file
> > modes of existing files and new files are added with the
> > correct file mode.
>
> Hmmm...I wonder why this is happening. It must have something to do with
> using ubuntu inside windows (and editing files in windows over samba).
Autsch. I thought as much.
> Nonetheless, I am having problems learning how to use git effectively. I
> am using some guide on kernel.com, but I wish I had some more detailed
> directions that were also less cryptic.
>
> when I type: git format-patch origin, can I edit the text in pico
> instead of vi?
export EDITOR='pico'
in your .bashrc will help.
> Stefan, one day you will stop getting all of these patch formating
> mistakes from me.
I'm looking forward... ;-)
> >If you (or any other) have no objection against my suggestions
>
> mentioned above, I'll change the code accordingly.
>
> No objection. That works fine too.
OK, I'll implement it this way.
Best regards,
Stefan
=====================================================================
DENX Software Engineering GmbH, HRB 165235 Munich, CEO: Wolfgang Denk
Office: Kirchenstr. 5, D-82194 Groebenzell, Germany
=====================================================================
prev parent reply other threads:[~2007-04-25 14:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-24 19:49 [U-Boot-Users] [PATCH] Fix AMCC bootstrap option letter label order Jeff Mann
2007-04-25 5:19 ` Stefan Roese
2007-04-25 8:10 ` Stefan Roese
2007-04-25 13:52 ` Jeff Mann
2007-04-25 14:14 ` Stefan Roese [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=200704251614.41535.sr@denx.de \
--to=sr@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox