Wolfgang Denk <w...@denx.de> wrote on 18/11/2009 23:45:56: > > Dear Joakim Tjernlund, > > In message <OFFB1B0130.660000EA-ONC1257672.00315799-C1257672. > 003a0...@transmode.se> you wrote: > > > > This was a "reply" for Mikes comment on > > [PATCH v2] crc32: Impl. linux optimized crc32() > > If it was a reply to "[PATCH v2] crc32: ..." then why didn't the > Subject read "Re: [PATCH v2] crc32: " ? > > > Would it been better for you if I just included the patch > > in a normal email reply? > > Sorry, I fail to understand what you mean here.
Hit the reply button for Mike's mail and just include the patch last in the reply. > > > > 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? Getting those headers is another story, our crappy mail system don't let me see headers easily :( > > > Anyhow, I can send a V3 version with everything in it to sum it up? > > Yes, please do, with clean commit message, s-o-b etc. Will do. _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
