On Tue, May 23, 2006 at 03:05:12PM +0200, Jakub Narebski wrote: > Peter Eriksen wrote: > > > On Tue, May 23, 2006 at 02:36:54PM +0200, Jakub Narebski wrote: > >> Peter Eriksen wrote: > >> > >> > Btw. > >> > > >> > I used these commands to produce the patch series: > >> > > >> > git diff --stat -C 24b65a30015aedd..pe/builtin > >> > git-send-email --no-chain-reply-to --compose \ > >> > --from=s022018@xxxxxxxxxxxxxx --not-signed-off-by-cc \ > >> > --quiet \ > >> > --subject="Make more commands builtin" \ > >> > --to=git@xxxxxxxxxxxxxxx Patches/* > >> > >> I wonder why the patches themselves are not replies to the main/summary > >> email, i.e. "Make more commands builtin" email... > > > > It seems thay are: > > > > Subject: Make more commands builtin > > Message-Id: <11483865361243-git-send-email-1> > > > > Subject: [PATCH 1/8] Builtin git-ls-files. > > Message-Id: <11483865362613-git-send-email-1> > > In-Reply-To: <11483865361243-git-send-email-1> > > Ahh... I'm reading git mailing list through GMane NNTP interface. > It would be nice if git-send-email added 'References:' Usenet/news > header in addition to email one 'In-Reply-To:'. Things would have worked better if --no-chain-reply-to had *not* been used, at least for those of us reading via mutt. I'm still in the process of getting my machines setup after moving, when I get sorted out, I'll try to look into this. - : send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html