Menu

#53 If not at top level of git tree, tkdiff reports "File xxx is not part of a revision control system"

v1.0 (example)
closed-fixed
None
5
2018-06-06
2017-10-14
Duncan Roe
No

I have top-level directory q with sub-directories help and q. tkdiff works fine on files at top level, but gives above error message for any file at lower level (e.g. tkdiff ./help/fndtn.qm fails as does cd help;tkdiff fndtn.qm).
I see Dorothy did something for svn trees, guess git needs something similar.
Will poke at this as time permits

Discussion

  • michael-m

    michael-m - 2018-04-15

    Actually, you are correct. I suspect this might date from the days when svn marked every directory with its signature hidden directory. Perhap when someone added the initial git support they just cloned the way it was handled for (then) svn, and no one noticed. I didn't see any indication though of what version you were running, so its difficult to pin down exactly, though I CAN tell you that the problem still occurs even in the 'official' release of the moment V4.2.
    Dorothys fix DID solve the issue for svn, but that's as far as it went. Another user contributed some newer GIT support to the next development version, but as I'm sure you've noticed there hasn't been a new release in some time. As I've personally also contributed some substantial new features (including a reworking of said new git support) you might find the development version more to your liking. I am actively trying to prepare that version for release, though I cant state when it might truely happen. But I will fixed your problem there.

     
  • michael-m

    michael-m - 2018-05-22
    • status: open --> accepted
    • assigned_to: michael-m
     
  • michael-m

    michael-m - 2018-06-06
    • status: accepted --> closed-fixed
     
  • michael-m

    michael-m - 2018-06-06

    You should no longer have trouble getting GIT to be recognized as your SCM. Be advised that your working directory still generally needs to be somewhere within the Git working copy tree, but it need not be at the topmost level. This has been fixed as of Version 4.3

     

Log in to post a comment.

MongoDB Logo MongoDB