From: Carl Worth <cworth@cworth.org>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] About faking message IDs
Date: Thu, 15 Oct 2009 17:14:09 -0700 [thread overview]
Message-ID: <1255651999-sup-9911@yoom.home.cworth.org> (raw)
In-Reply-To: <1255620476-sup-8113@masanjin.net>
[-- Attachment #1.1: Type: text/plain, Size: 380 bytes --]
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
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
[-- Attachment #2: Type: text/plain, Size: 140 bytes --]
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
prev parent reply other threads:[~2009-10-16 0:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-15 10:50 Michael Stapelberg
2009-10-15 13:47 ` William Morgan
2009-10-15 13:59 ` Michael Stapelberg
2009-10-15 15:29 ` William Morgan
2009-10-15 19:21 ` Nicolas Pouillard
2009-10-16 0:14 ` Carl Worth [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1255651999-sup-9911@yoom.home.cworth.org \
--to=cworth@cworth.org \
--cc=sup-talk@rubyforge.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox