[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [TSVN] Some extremely minor glitches

From: SteveKing <steveking_at_gmx.ch>
Date: 2004-10-12 19:20:37 CEST

Roel Harbers wrote:

> - When I choose "revert" on a folder, but then uncheck all changed
> items, I can still click Ok. When I do, I get an error:
> '.' is not a working copy. This should probably be more along the lines
> of "Nothing to revert" (or ok should be disabled)

Done in revision 1815.

> - When I use the context menu in the commit dialog to add a
> non-versioned file to the ignore-list, the P-only change of the parent
> (the svn:ignore property) is not displayed in the list of things to
> commit. It is (correctly) commited however. I would expect the
> to-be-committed list to be refreshed with the P-only change of the dir
> after ignoring a file.

Please note that the p-only change is only committed if you don't
deselect an entry from being committed. If you deselect one or more
entries, that p-only change isn't committed. So it's even worse than you
describe it :(

So I fixed that in revision 1816.

> - When unselecting a directory in the commit dialog, all files under
> that directory are unselected too, EVEN when it's a P-only change. I
> understand it is useful for adds, but why for p-changes? I would expect
> that not commiting a p-change for a directory would still commit
> changes to files in that directory.

I think you'll have to live with that.

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Wed Oct 13 08:39:58 2004

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.