Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion sh.addTagRange

Received: by 10.58.222.100 with SMTP id ql4mr5437180vec.22.1349202737466;
        Tue, 02 Oct 2012 11:32:17 -0700 (PDT)
X-BeenThere: mongodb-user@googlegroups.com
Received: by 10.220.154.17 with SMTP id m17ls641048vcw.1.gmail; Tue, 02 Oct
 2012 11:32:07 -0700 (PDT)
Received: by 10.52.71.38 with SMTP id r6mr3590520vdu.12.1349202727693;
        Tue, 02 Oct 2012 11:32:07 -0700 (PDT)
Date: Tue, 2 Oct 2012 11:32:07 -0700 (PDT)
From: Marco Schirrmeister <mschirrmeis...@gmail.com>
To: mongodb-user@googlegroups.com
Message-Id: <5318c955-1c3c-415a-a2d0-9bc0bd1381b6@googlegroups.com>
In-Reply-To: <bb82cacc-cd94-4a6d-becf-65c141e42a49@googlegroups.com>
References: <b3499f29-d480-4060-8dc2-cdb60eaa55f4@googlegroups.com>
 <bb82cacc-cd94-4a6d-becf-65c141e42a49@googlegroups.com>
Subject: Re: sh.addTagRange
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_217_13227263.1349202727309"

------=_Part_217_13227263.1349202727309
Content-Type: multipart/alternative; 
	boundary="----=_Part_218_12503121.1349202727309"

------=_Part_218_12503121.1349202727309
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit



On Tuesday, October 2, 2012 5:37:19 PM UTC+2, Asya Kamsky wrote:
>
> There is a bug that's going to be fixed in 2.2.1 - it should be out very 
> soon.
> Meanwhile you can try the release candidate and see that it fixes the 
> problem.
>
> https://jira.mongodb.org/browse/SERVER-6943
>

Thank you.
I will give that a try.



------=_Part_218_12503121.1349202727309
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<br><br>On Tuesday, October 2, 2012 5:37:19 PM UTC+2, Asya Kamsky wrote:<blockquote class="gmail_quote" style="margin: 0;margin-left: 0.8ex;border-left: 1px #ccc solid;padding-left: 1ex;">There is a bug that's going to be fixed in 2.2.1 - it should be out very soon.<div>Meanwhile you can try the release candidate and see that it fixes the problem.</div><div><br></div><div><a href="https://jira.mongodb.org/browse/SERVER-6943" target="_blank">https://jira.mongodb.org/<wbr>browse/SERVER-6943</a></div></blockquote><div><br></div><div>Thank you.</div><div>I will give that a try.</div><div><br></div><div><br></div>
------=_Part_218_12503121.1349202727309--

------=_Part_217_13227263.1349202727309--