From: Jerry Van Baren <gvb.uboot@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] fix system config overwrite @ MPC834x
Date: Sat, 19 Apr 2008 08:55:58 -0400 [thread overview]
Message-ID: <4809EBDE.2040905@gmail.com> (raw)
In-Reply-To: <20080418112046.ce82252a.kim.phillips@freescale.com>
Kim Phillips wrote:
> On Fri, 18 Apr 2008 10:48:51 +0200
> Andre Schwarz <andre.schwarz@matrix-vision.de> wrote:
>
>> Kim,
>>
>> doing a git-pull gives "Already up-to-date."
>> The patch is produced with "git-diff --patch-with-stat
>> cpu/mpc83xx/cpu_init.c"
>
> using git-commit and git-format-patch is recommended, but that's
> probably not the problem here. Have you followed the instructions for
> Thunderbird in linux-2.6/Documentation/email-clients.txt? You can test
> by using git-am on patches you email yourself.
>
> Kim
Hi Andre,
Another thing I do when something I think should work doesn't is to make
a fresh clone of the git repository, apply my new patch to it, and
regenerate the patch from that. Sometimes I get confused as to the
state of my working directory, what has been applied to it, what I've
pulled from, etc. (I used to be really sharp, but then I discovered
beer and the edges are a little duller now.)
FWIIW, I keep a local pristine copy of the denx.de master repository
(and others I am interested in), doing a nightly pull in a cron job.
This allows me to make a new working clone of what should be a clean
repository without hammering denx.de. Worst case, I hammer denx.de
occasionally. :-/
Best regards,
gvb
prev parent reply other threads:[~2008-04-19 12:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-17 17:28 [U-Boot-Users] [PATCH] fix system config overwrite @ MPC834x Andre Schwarz
2008-04-17 20:56 ` Kim Phillips
2008-04-18 8:48 ` Andre Schwarz
2008-04-18 16:20 ` Kim Phillips
2008-04-18 18:31 ` André Schwarz
2008-04-19 12:55 ` Jerry Van Baren [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=4809EBDE.2040905@gmail.com \
--to=gvb.uboot@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