Skip Menu |

This queue is for tickets about the App-SVN-Bisect CPAN distribution.

Report information
The Basics
Id: 46566
Status: resolved
Priority: 0/
Queue: App-SVN-Bisect
People
Owner: Nobody in particular
Requestors: coke [...] cpan.org
Cc:
AdminCc:
Bug Information
Severity: Normal
Broken in: 0.8
Fixed in: (no value)

History Show all quoted text
  Mon Jun 01 02:06:27 2009 coke [...] cpan.org - Ticket created
Subject: --max's error message is confusing
if a repository has versions greater than the directory you have checked out, svn info reports a higher number than the last revision for that directory. --max reports the last actual commit for that directory instead. It would be nice if max just silently translated the max revision of the repo to the max revision of the directory, or if instead of saying "repository maximum", "repository maximum for this directory." Regards, thanks for making my svn bisect app obsolete. =-)
  Mon Jun 01 07:06:33 2009 INFINOID [...] cpan.org - Correspondence added
On Mon Jun 01 02:06:27 2009, COKE wrote: Show quoted text
> if a repository has versions greater than the directory you have checked > out, svn info reports a higher number than the last revision for that > directory. --max reports the last actual commit for that directory > instead. > > It would be nice if max just silently translated the max revision of the > repo to the max revision of the directory, or if instead of saying > "repository maximum", "repository maximum for this directory."
Hi Will, thanks for the report. It would help me to know how you were actually using svn-bisect. What command-line did you use? Did you run it on parrot? Where did you run it? What output did you get? What output did you expect? I've been working on a feature where it will limit itself to a subdirectory when fetching the revision history, thus focusing on a specific subset of the log. At first I thought you were using that, which was a little confusing because I don't think I've finished writing that yet, let alone released it. So, were you running it in a subdir of parrot? Thanks, Mark
  Mon Jun 01 07:06:34 2009 The RT System itself - Status changed from 'new' to 'open'
  Mon Jun 01 09:02:38 2009 coke [...] cpan.org - Correspondence added
On Mon Jun 01 07:06:33 2009, INFINOID wrote: Show quoted text
> On Mon Jun 01 02:06:27 2009, COKE wrote:
> > if a repository has versions greater than the directory you have
checked Show quoted text
> > out, svn info reports a higher number than the last revision for
that Show quoted text
> > directory. --max reports the last actual commit for that directory > > instead. > > > > It would be nice if max just silently translated the max revision of
the Show quoted text
> > repo to the max revision of the directory, or if instead of saying > > "repository maximum", "repository maximum for this directory."
> > Hi Will, thanks for the report. > > It would help me to know how you were actually using svn-bisect. What > command-line did you use? Did you run it on parrot? Where did you
run Show quoted text
> it? What output did you get? What output did you expect? > > I've been working on a feature where it will limit itself to a > subdirectory when fetching the revision history, thus focusing on a > specific subset of the log. At first I thought you were using that, > which was a little confusing because I don't think I've finished
writing Show quoted text
> that yet, let alone released it. So, were you running it in a subdir
of Show quoted text
> parrot?
Well, the subdir was trunk - but at the time I did it, there were a dozen commits after that in a branch; So --max was reporting something like r99, when I had just svn up'd trunk to r110 - just that r100:110 occurred somewhere other than trunk. [1] Show quoted text
> Thanks, > > Mark
[1] Obviously, these aren't the actual numbers.
  Mon Jun 01 09:05:00 2009 INFINOID [...] cpan.org - Correspondence added
On Mon Jun 01 09:02:38 2009, COKE wrote: Show quoted text
> Well, the subdir was trunk - but at the time I did it, there were a > dozen commits after that in a branch; So --max was reporting something > like r99, when I had just svn up'd trunk to r110 - just that r100:110 > occurred somewhere other than trunk. [1]
Ok, thanks. Would "revision history maximum" be clearer than "repository maximum", then? Mark
  Mon Jun 01 09:09:49 2009 will [...] coleda.com - Correspondence added
CC: coke [...] cpan.org
Subject: Re: [rt.cpan.org #46566] --max's error message is confusing
Date: Mon, 1 Jun 2009 09:08:28 -0400
To: bug-App-SVN-Bisect [...] rt.cpan.org
From: Will Coleda <will [...] coleda.com>
On Mon, Jun 1, 2009 at 9:05 AM, Mark Glines via RT <bug-App-SVN-Bisect@rt.cpan.org> wrote: Show quoted text
> <URL: https://rt.cpan.org/Ticket/Display.html?id=46566 > > > On Mon Jun 01 09:02:38 2009, COKE wrote:
>> Well, the subdir was trunk - but at the time I did it, there were a >> dozen commits after that in a branch; So --max was reporting something >> like r99, when I had just svn up'd trunk to r110 - just that r100:110 >> occurred somewhere other than trunk. [1]
> > Ok, thanks.  Would "revision history maximum" be clearer than > "repository maximum", then? > > Mark
something that references the fact that it's just this particular checkout would be nice. "working directory maximum revision", perhaps? -- Will "Coke" Coleda
  Mon Jun 01 09:42:57 2009 INFINOID [...] cpan.org - Correspondence added
On Mon Jun 01 09:09:49 2009, will@coleda.com wrote: Show quoted text
> On Mon, Jun 1, 2009 at 9:05 AM, Mark Glines via RT > <bug-App-SVN-Bisect@rt.cpan.org> wrote:
> > <URL: https://rt.cpan.org/Ticket/Display.html?id=46566 > > > > > On Mon Jun 01 09:02:38 2009, COKE wrote:
> >> Well, the subdir was trunk - but at the time I did it, there were a > >> dozen commits after that in a branch; So --max was reporting something > >> like r99, when I had just svn up'd trunk to r110 - just that r100:110 > >> occurred somewhere other than trunk. [1]
> > > > Ok, thanks.  Would "revision history maximum" be clearer than > > "repository maximum", then? > > > > Mark
> > something that references the fact that it's just this particular > checkout would be nice.
Ok, now I'm starting to see the benefit of silently translating the max revision of the repo to the max revision of the directory. (Or maybe I'll just change the error into a warning and proceed with the real maximum.) Show quoted text
> "working directory maximum revision", perhaps?
That's perfectly clear, but it's getting too huge for a simple error message. Thanks, I think I'll try the other route. Mark
  Thu Nov 19 06:58:03 2009 INFINOID [...] cpan.org - Correspondence added
On Mon Jun 01 09:09:49 2009, will@coleda.com wrote: Show quoted text
> "working directory maximum revision", perhaps?
Message changed to "working directory maximum" in 0.9. Thanks!
  Thu Nov 19 06:58:05 2009 INFINOID [...] cpan.org - Status changed from 'open' to 'resolved'