From: "Markus Klotzbücher" <mk@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] Fix possible uninitialized variable compiler warning.
Date: Thu, 12 Oct 2006 11:16:24 +0200 [thread overview]
Message-ID: <8764ep7v2v.fsf@denx.de> (raw)
In-Reply-To: <1160634465.4993.1.camel@localhost> (Matthew McClintock's message of "Thu, 12 Oct 2006 01:27:44 -0500")
Hi Matthew,
Matthew McClintock <msm@freescale.com> writes:
> If you would like I can start over and recommit each patch. Do you have
> any better methods of updating the CHANGELOG for each patch?
Its probably* too late in this case, but in general stacked git lets you
handle this efficently. You can maintain a stack of patches on top of
the cloned official repo. When you think your done, commit the patches
to a branch and publish it. If it needs further fixes, delete the
branch, fix you patches repeat the commit and publish.
Regards
Markus Klotzbuecher
* There is a "stg uncommit" command, that allows you to turn a git
commit into a stacked git patch, but I havn't used that one yet.
prev parent reply other threads:[~2006-10-12 9:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-10 6:23 [U-Boot-Users] [PATCH] Fix possible uninitialized variable compiler warning Grant Likely
2006-10-10 7:05 ` Wolfgang Denk
2006-10-10 7:13 ` Grant Likely
2006-10-10 8:58 ` Wolfgang Denk
2006-10-11 6:09 ` Grant Likely
2006-10-11 7:44 ` Wolfgang Denk
2006-10-11 15:30 ` Grant Likely
2006-10-11 17:14 ` Haavard Skinnemoen
2006-10-11 20:10 ` Wolfgang Denk
2006-10-12 19:08 ` Grant Likely
2006-10-12 20:26 ` Wolfgang Denk
2006-10-12 20:51 ` Grant Likely
2006-10-13 0:13 ` Wolfgang Denk
2006-10-11 18:22 ` Matthew McClintock
2006-10-11 18:29 ` Grant Likely
2006-10-11 20:34 ` Wolfgang Denk
2006-10-11 21:02 ` Matthew McClintock
2006-10-11 21:55 ` Wolfgang Denk
2006-10-11 22:04 ` Wolfgang Denk
2006-10-12 6:27 ` Matthew McClintock
2006-10-12 9:16 ` Markus Klotzbücher [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=8764ep7v2v.fsf@denx.de \
--to=mk@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