Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759063AbXIQUrU (ORCPT ); Mon, 17 Sep 2007 16:47:20 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756361AbXIQUrH (ORCPT ); Mon, 17 Sep 2007 16:47:07 -0400 Received: from z2.cat.iki.fi ([212.16.98.133]:38417 "EHLO z2.cat.iki.fi" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751918AbXIQUrG (ORCPT ); Mon, 17 Sep 2007 16:47:06 -0400 Date: Mon, 17 Sep 2007 23:47:01 +0300 From: Matti Aarnio To: Junio C Hamano Cc: Adrian Bunk , Avi Kivity , linux-kernel@vger.kernel.org, git@vger.kernel.org Subject: Re: git-send-email creates duplicate Message-Id's Message-ID: <20070917204701.GU6372@mea-ext.zmailer.org> References: <11900179463203-git-send-email-avi@qumranet.com> <20070917155901.GP18232@stusta.de> <7vejgxyrde.fsf@gitster.siamese.dyndns.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7vejgxyrde.fsf@gitster.siamese.dyndns.org> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1917 Lines: 44 On Mon, Sep 17, 2007 at 01:22:05PM -0700, Junio C Hamano wrote: > Adrian Bunk writes: > > > The following might be a bug in git-send-email (git maintainers Cc'ed > > and KVM list removed from Cc): > > > > Patch 54 got the same Message-Id as patch 61 and patch 89 got the same > > Message-Id as patch 104. > > ... > > The emails are: > > http://marc.info/?l=linux-kernel&m=119002061330270&w=2 > > http://marc.info/?l=linux-kernel&m=119002059626434&w=2 > > http://marc.info/?l=linux-kernel&m=119002060011801&w=2 > > http://marc.info/?l=linux-kernel&m=119002060318915&w=2 > > The old code generated rand(4200) for each message and appended > it to the timestamp. I do not know where the original author > got 4200 from, but I think if you send many messages within a > single second it is possible to get collisions. > > I guess something like this patch is an improvement? It > generates a single prefix from timestamp and random, and appends > a number that is incremented for each message. Much better. You may also consider a possibility of letting your local MTA do the Message-ID generation, unless you are tracking something with it and thus need to know the generated values. .. but apparently git much prefers sending email by SMTP, where the message-id must be present, or one really should block any such emails.. (except that systems like qmail send error messages without message-id ...) My own recipe is: sprintf("%d-%d-%d", time , getpid, ++localsequence) catenate on that your favourite domain name where that recipe is likely to be valid, and you are all set. /Matti Aarnio -- one of - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/