Feature #204

Scn only the HEAD revision

Added by Christian Dehning 976 days ago. Updated 966 days ago.

Status:Closed Start:
Priority:Normal Due date:
Assigned to:Karl Heinz Marbaise % Done:

100%
Category:CLI
Target version:0.6.1 Bestla

Description

It would be usefull, if there would be a scan command for scanning the head-revision only.

Something like this would need to stand in ScanCommand.java:

public Long getFromRev (CommandLine cline) {
    List<String> list = cline.getValues((getOptionFromRev()));
    if (list == null || list.size() == 0) {
        //Default value for --fromrev
        return new Long(1);
    } else if (list.get(0) == "HEAD") {
        return SVNRevision.HEAD.getNumber();
    } else {
        return Long.parseLong(list.get(0));
    }
}

History

Updated by Karl Heinz Marbaise 976 days ago

Hi Christian,

It would be usefull, if there would be a scan command for scanning the head-revision only.

Would that be needed just for the scan command or is the intention different ?

Kind regards
Karl Heinz Marbaise

Updated by Karl Heinz Marbaise 976 days ago

Karl Heinz Marbaise wrote:

Hi Christian,

It would be usefull, if there would be a scan command for scanning the head-revision only.

Would that be needed just for the scan command or is the intention different ?

EDIT: If you like to scan always the last changes in a repository you can use the schedule command of SupoSE...

Kind regards Karl Heinz Marbaise

Updated by Christian Dehning 976 days ago

EDIT: If you like to scan always the last changes in a repository you can use the schedule command of SupoSE...

I'm sry, but that would still mean i would have to scan the whole repository once, right? That would be a very big scan, which I just don't need ;)

In my case it would be sufficient to only have an index of the head revision... Everything else would produce a very huge index, on which searching won't be fun.

(please read in my next ticket for another reason ...)

Updated by Karl Heinz Marbaise 976 days ago

Hello Christian,

Everything else would produce a very huge index, on which searching won't be fun.

This depends on what you mean with "huge index". I have repository scan which produce a 7 GB Index...and it's very helpful to search in all the revision...but this is only my opinion...

Kind regards
Karl Heinz Marbaise

Updated by Karl Heinz Marbaise 976 days ago

  • Assigned to set to Karl Heinz Marbaise
  • Target version set to 24
  • Start deleted (06/03/2009)

Updated by Christian Dehning 976 days ago

  • Assigned to deleted (Karl Heinz Marbaise)
  • Target version deleted (24)

This depends on what you mean with "huge index". I have repository scan which produce a 7 GB Index...and it's very helpful to search in all the revision...but this is only my opinion...

It is helpfull indeed, but hard to realize when my index will rise far above the 100GB... ;)

Updated by Karl Heinz Marbaise 976 days ago

  • Assigned to set to Karl Heinz Marbaise
  • Target version set to 24

Hi Christian,

It is helpfull indeed, but hard to realize when my index will rise far above the 100GB... ;)

Ok. This is a real huge index...

Updated by kama - 972 days ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100

Applied in changeset r362.

Updated by Karl Heinz Marbaise 966 days ago

  • Target version changed from 24 to 0.6.1 Bestla

Also available in: Atom PDF