tools/Makefile cleanup and win32 tool support
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v3 Latest posting 2/20 of 28 patches 0 repliesNew
- v3 posting 1/228 patches 0 repliesSuperseded
- v226 patches 0 repliesSuperseded
Earlier versions · 1
| Version | Posted | Patches | Replies | Status |
|---|---|---|---|---|
| v1 | 15 patches | 0 replies | Superseded |
Patches in v3 posting 2/2 No applies recorded yet
None of the 28 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v3 yet.
Cover letter [U-Boot] [PATCH/next v3 00/28] tools/Makefile cleanup and win32 tool support
Quoted 20 lines · Mike Frysinger
Quoted 8 lines · On Tuesday 17 March 2009 13:21:05 Scott Wood wrote:
Quoted 6 lines · Peter Tyser
This patch series attempts to do 2 things:
1. Add support for generating win32 versions of the tools intools/
2. Cleanuptools/MakefilesomewhatIn the process of #1 I couldn't help but work on #2 a bit:) Let me know if people would prefer the patches split up.
Quoted 7 lines
<peeve type="pet">
It's easier to read patchsets, especially large ones, when each message is a reply to the original rather than to the preceding patch (which in many mailers makes the subjects appear shifted one character to the right compared to the parent post, eventually scrolling off the right edge of the screen).
</peeve>your mailer does just one char ? i should switch from kmail to whatever you're using :) ...
Quoted 8 lines
Peter: if you update to git-1.6.2 (well, maybe what i describe happens in earlier versions, but i know 1.6.2 is good), then you can use --cover-letter to
git format-patchandgit send-emailwill thread things the way Scott describes if you send all the patches together:git send-email 0*.patch.the cover letter will be the thread starter and all the patches in the series will refer to that one rather than each N patch referring to N-1 in the series.
I see similar default threading styles in both 1.6.0 and 1.6.2. It looks like I was missing git send-email's "--no-chain-reply-to" argument. I added "sendmail.chainreplyto = false" to my .gitconfig which also does the trick.
It makes me wonder why --chain-reply-to would ever be the default...
Peter