You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Daniel Kulp (JIRA)" <ji...@apache.org> on 2010/01/08 18:54:54 UTC
[jira] Created: (INFRA-2423) Certain date ranges aren't working for
logs
Certain date ranges aren't working for logs
-------------------------------------------
Key: INFRA-2423
URL: https://issues.apache.org/jira/browse/INFRA-2423
Project: Infrastructure
Issue Type: Bug
Security Level: public (Regular issues)
Components: Subversion
Reporter: Daniel Kulp
Priority: Trivial
While trying to determine an SVN revision number that fixed something reported on the mailing list, I discovered some date ranges aren't working properly.
Example:
Works fine, lists all the commits in the range:
svn log -r "{20090616}:{20091120}" -q http://svn.eu.apache.org/repos/asf/cxf/trunk
Only lists the commits after Nov-15
svn log -r "{20090617}:{20091120}" -q http://svn.eu.apache.org/repos/asf/cxf/trunk
Doesn't list any commits:
svn log -r "{20090617}:{20091115}" -q http://svn.eu.apache.org/repos/asf/cxf/trunk
Jun-17 and Nov-15 seem to be the magic dates. Not sure what happened on those dates that would cause this. (Subversion was imported on Nov-15, not sure why that would affect anything)
Anyway, nothing critical, but very strange.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-2423) Certain date ranges aren't working
for logs
Posted by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798190#action_12798190 ]
#asfinfra IRC Bot commented on INFRA-2423:
------------------------------------------
<joes4> wish not granted.
> Certain date ranges aren't working for logs
> -------------------------------------------
>
> Key: INFRA-2423
> URL: https://issues.apache.org/jira/browse/INFRA-2423
> Project: Infrastructure
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Subversion
> Reporter: Daniel Kulp
> Priority: Trivial
>
> While trying to determine an SVN revision number that fixed something reported on the mailing list, I discovered some date ranges aren't working properly.
> Example:
> Works fine, lists all the commits in the range:
> svn log -r "{20090616}:{20091120}" -q http://svn.eu.apache.org/repos/asf/cxf/trunk
> Only lists the commits after Nov-15
> svn log -r "{20090617}:{20091120}" -q http://svn.eu.apache.org/repos/asf/cxf/trunk
> Doesn't list any commits:
> svn log -r "{20090617}:{20091115}" -q http://svn.eu.apache.org/repos/asf/cxf/trunk
> Jun-17 and Nov-15 seem to be the magic dates. Not sure what happened on those dates that would cause this. (Subversion was imported on Nov-15, not sure why that would affect anything)
> Anyway, nothing critical, but very strange.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-2423) Certain date ranges aren't working
for logs
Posted by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798193#action_12798193 ]
#asfinfra IRC Bot commented on INFRA-2423:
------------------------------------------
<pquerna> ... and assumes that all revs are in a sequence, which is not true for the ASF repository.
> Certain date ranges aren't working for logs
> -------------------------------------------
>
> Key: INFRA-2423
> URL: https://issues.apache.org/jira/browse/INFRA-2423
> Project: Infrastructure
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Subversion
> Reporter: Daniel Kulp
> Priority: Trivial
>
> While trying to determine an SVN revision number that fixed something reported on the mailing list, I discovered some date ranges aren't working properly.
> Example:
> Works fine, lists all the commits in the range:
> svn log -r "{20090616}:{20091120}" -q http://svn.eu.apache.org/repos/asf/cxf/trunk
> Only lists the commits after Nov-15
> svn log -r "{20090617}:{20091120}" -q http://svn.eu.apache.org/repos/asf/cxf/trunk
> Doesn't list any commits:
> svn log -r "{20090617}:{20091115}" -q http://svn.eu.apache.org/repos/asf/cxf/trunk
> Jun-17 and Nov-15 seem to be the magic dates. Not sure what happened on those dates that would cause this. (Subversion was imported on Nov-15, not sure why that would affect anything)
> Anyway, nothing critical, but very strange.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (INFRA-2423) Certain date ranges aren't working for
logs
Posted by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
#asfinfra IRC Bot closed INFRA-2423.
------------------------------------
Resolution: Won't Fix
> Certain date ranges aren't working for logs
> -------------------------------------------
>
> Key: INFRA-2423
> URL: https://issues.apache.org/jira/browse/INFRA-2423
> Project: Infrastructure
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Subversion
> Reporter: Daniel Kulp
> Priority: Trivial
>
> While trying to determine an SVN revision number that fixed something reported on the mailing list, I discovered some date ranges aren't working properly.
> Example:
> Works fine, lists all the commits in the range:
> svn log -r "{20090616}:{20091120}" -q http://svn.eu.apache.org/repos/asf/cxf/trunk
> Only lists the commits after Nov-15
> svn log -r "{20090617}:{20091120}" -q http://svn.eu.apache.org/repos/asf/cxf/trunk
> Doesn't list any commits:
> svn log -r "{20090617}:{20091115}" -q http://svn.eu.apache.org/repos/asf/cxf/trunk
> Jun-17 and Nov-15 seem to be the magic dates. Not sure what happened on those dates that would cause this. (Subversion was imported on Nov-15, not sure why that would affect anything)
> Anyway, nothing critical, but very strange.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-2423) Certain date ranges aren't working
for logs
Posted by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798192#action_12798192 ]
#asfinfra IRC Bot commented on INFRA-2423:
------------------------------------------
<pquerna> little more detail: this is strictly speaking a bug in subversion, if you load a repos with revs, it breaks all support for date based queries, because fsfs doesn't ahve secondary indexes based on date.
> Certain date ranges aren't working for logs
> -------------------------------------------
>
> Key: INFRA-2423
> URL: https://issues.apache.org/jira/browse/INFRA-2423
> Project: Infrastructure
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Subversion
> Reporter: Daniel Kulp
> Priority: Trivial
>
> While trying to determine an SVN revision number that fixed something reported on the mailing list, I discovered some date ranges aren't working properly.
> Example:
> Works fine, lists all the commits in the range:
> svn log -r "{20090616}:{20091120}" -q http://svn.eu.apache.org/repos/asf/cxf/trunk
> Only lists the commits after Nov-15
> svn log -r "{20090617}:{20091120}" -q http://svn.eu.apache.org/repos/asf/cxf/trunk
> Doesn't list any commits:
> svn log -r "{20090617}:{20091115}" -q http://svn.eu.apache.org/repos/asf/cxf/trunk
> Jun-17 and Nov-15 seem to be the magic dates. Not sure what happened on those dates that would cause this. (Subversion was imported on Nov-15, not sure why that would affect anything)
> Anyway, nothing critical, but very strange.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.