From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.90.117.16 with SMTP id p16cs654816agc; Thu, 15 Oct 2009 17:14:19 -0700 (PDT) Received: by 10.224.25.3 with SMTP id x3mr622931qab.159.1255652057577; Thu, 15 Oct 2009 17:14:17 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 3si1053670qyk.0.2009.10.15.17.14.17; Thu, 15 Oct 2009 17:14:17 -0700 (PDT) Received-SPF: pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 3593118582D5; Thu, 15 Oct 2009 20:14:17 -0400 (EDT) Received: from olra.theworths.org (olra.theworths.org [82.165.184.25]) by rubyforge.org (Postfix) with ESMTP id CBC551858277 for ; Thu, 15 Oct 2009 20:14:04 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id C5A5A4028BF for ; Thu, 15 Oct 2009 17:14:03 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org Received: from olra.theworths.org ([127.0.0.1]) by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id quVdQdMjw1YW for ; Thu, 15 Oct 2009 17:14:03 -0700 (PDT) Received: from cworth.org (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id CA1284041FF for ; Thu, 15 Oct 2009 17:14:02 -0700 (PDT) From: Carl Worth To: sup-talk In-reply-to: <1255620476-sup-8113@masanjin.net> References: <1255603625-sup-2558@midna.zekjur.net> <1255614431-sup-5910@masanjin.net> <1255615018-sup-5653@midna.zekjur.net> <1255620476-sup-8113@masanjin.net> Date: Thu, 15 Oct 2009 17:14:09 -0700 Message-Id: <1255651999-sup-9911@yoom.home.cworth.org> User-Agent: Sup/git MIME-Version: 1.0 Subject: Re: [sup-talk] About faking message IDs X-BeenThere: sup-talk@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: User & developer discussion of Sup List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1528135189==" Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org --===============1528135189== Content-Transfer-Encoding: 8bit Content-Type: multipart/signed; micalg="pgp-sha1"; boundary="=-1255652049-381386-15235-4925-7-="; protocol="application/pgp-signature" --=-1255652049-381386-15235-4925-7-= Content-Type: text/plain; charset=UTF-8 Excerpts from William Morgan's message of Thu Oct 15 08:29:29 -0700 2009: > Ok. I think it's fine to generate the message id via another mechanism, > e.g. the way we do it in edit-message-mode ("<#{Time.now.to_i}-sup-#{rand > 10000}@#{hostname}"). Won't that then make sup insert duplicate documents into the index for any run of sup-sync --all over the relevant sources? -Carl --=-1255652049-381386-15235-4925-7-= Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iD8DBQFK17rR6JDdNq8qSWgRAjvmAJ9pgHqfrmJ6mXLgNTBAFiLOF8nOZQCgnzR+ DzpFRD5YvCDNx4q9rfIPO3E= =Fn1Q -----END PGP SIGNATURE----- --=-1255652049-381386-15235-4925-7-=-- --===============1528135189== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk --===============1528135189==--