« first day (489 days earlier)      last day (1171 days later) » 

6:32 PM
@SethJ That's a good question. I'm not sure how we handle that considering his is older. I'm going to close this now in the meantime while we discuss. Also consider just editing in more details to Shalom's question: it would improve the question without changing his intent. — Double AA 38 mins ago
@msh210 @DoubleAA In the past we've merged an older Q into a newer one when the Qs were identical in intent but the newer one was worded better or had attracted better answers. Here, the newer one is definitely worded better but I'm not sure that the old one has the same intent as the new one (as @sethj points out in the comments) (though I do think one Q should be closed). So I don't know that we have any precedent. Nonetheless [cont'd]
[cont'd] my own personal feeling is that we can merge the older one to the newer one (and comment on each merged answer that it was to a different question). What does everyone else think?
 
@msh210 either...or?
 
@DoubleAA Heh. Um, what did I mean to write? Oh, yes. lemme edit that... ...done.
 
 
1 hour later…
7:45 PM
@msh210 I agree with merging the answers from the older one into the newer one, marking them as answers to a different question, and closing the older as a dup of the newer.
 

« first day (489 days earlier)      last day (1171 days later) » 
http://chat.stackexchange.com/transcript/message/6109926
chat.stackexchange.com
crawl=CC-MAIN-2015-48
15259
application/http; msgtype=response
sha1:53TFDG5CPMSDH4YVROKXCJNLPDXJBXSQ
<urn:uuid:cde6f512-ff2c-44c0-8c9a-aba583e64a67>
2015-11-26T15:58:25Z
198.252.206.29
sha1:VGB5IXRLHDZSALSDGYOFQMSRVS7NH3GQ
<urn:uuid:fb0610aa-04ef-4f92-afad-c422323ee955>
http://chat.stackexchange.com/transcript/message/6109926
response
<urn:uuid:77ddd527-91b8-46e3-9a38-d32071fea34d>
robots: classic
hostname: ip-10-71-132-137.ec2.internal
software: Nutch 1.6 (CC)/CC WarcExport 1.0
isPartOf: CC-MAIN-2015-48
operator: CommonCrawl Admin
description: Wide crawl of the web for Nov 2015
publisher: CommonCrawl
format: WARC File Format 1.0
conformsTo: http://bibnum.bnf.fr/WARC/WARC_ISO_28500_version1_latestdraft.pdf