From: Mike Frysinger Date: Wed, 18 Nov 2009 18:45:16 -0500 Subject: [U-Boot] [PATCH] crc32: Make crc32 build on non Linux too In-Reply-To: References: <1258446374-2919-1-git-send-email-Joakim.Tjernlund@transmode.se> <20091118224556.C1A083F6C2@gemini.denx.de> Message-ID: <200911181845.17153.vapier@gentoo.org> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Wednesday 18 November 2009 17:59:59 Joakim Tjernlund wrote: > Wolfgang Denk wrote on 18/11/2009 23:45:56: > > Joakim Tjernlund wrote: > > > > And PLEASE keep the In-reply-to: and References: headers so threading > > > > of the messages works. > > > > > > Since this was a new email sent with git, I don't In-reply-to: and > > > References: should be there? > > > > You do reply to this thread. And "git send-email" asks you to provide > > the message Id's: > > > > Message-ID to be used as In-Reply-To for the first email? > > > > Please do not ignore this. > > I familiar on when it is appropriate to use In-reply-to:/References: > You mean even if a send a new mail(a git patch in this case) with a > new subject, I should still add those two headers? yes > Getting those headers is another story, our crappy mail system don't let > me see headers easily :( it should be relatively easy to obtain via gmane. but i'm pretty sure every MS based e-mail system has support for 'view source', and certainly every open source e-mail client does. -mike -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 836 bytes Desc: This is a digitally signed message part. Url : http://lists.denx.de/pipermail/u-boot/attachments/20091118/114bb46a/attachment.pgp