Olga-

AFAICT, since installing the latest versions of the VisualSVN plug-in
and TortoiseSVN on my client PCs yesterday, I am not experiencing any
problems other than the missing Log history.

BTW, it is *not* just the 6 Commits that are missing; it is *all* the
Commits between the original Add of the files and the Commit yesterday
that finally showed up, only after I installed the latest versions of
VisualSVN plug-in and TortoiseSVN and re-booted. I suspect we are
talking as many as 2 dozen missing Commits, as I Commit regularly,
often 5 or more times a day, when working on a file, and in the last
week I have been working mainly on the one particular problem file I
am referring to. I mentioned 6 as a number only because I am
absolutely sure it was *at least* that many Commits in the last week.
It's likely to be more, but I am *sure* of at least 6.

I will speak from now on of one problem file, a code file named
frmMain.vb, which is representative of the problem files, rather than
confusing the issue by referring to all of the problem files, but
please keep in mind that there are several files exhibiting this
issue.

According to what is showing now in the Log, the original Add of
frmMain.vb was revision 79 - this seems possible, as the Log states
that the file was Added to SVN on Feb. 26, 2009, and Windows Explorer
shows that the file was created on Monday, ‎October ‎06, ‎2008,
‏‎7:06:32 PM. I didn't set up SVN on the server until Jan. 2009.

The *only* other entry that shows in the Log is the Commit I did last
night. The Log states it is revision 117, and it was Committed
yesterday. As noted above, I Commit regularly, often 5 or more times a
day, when working on a file, and in the last week I have been working
mainly on this one file and its related .Designer.vb file. At a guess
I would say there are at least 15-20 missing Commits for this one
file.


I will gather the other information you asked for and will get back to
you.


Thanks,

-Andrew



Reply via email to