On Fri, Feb 26, 2016 at 3:54 PM, Jacob Weber <jacob_at_jacobweber.com> wrote:
> Reverting a bit change in Subclipse is kind of a nightmare -- you have to
> go through several rounds of Team > Revert, each one slowly reverting one
> file at a time. There's got to be a better way.
I cannot recall a single occasion in 10+ years I have had to do this. So
what is the specific scenario you have where this is necessary? Please
provide more details. How does TortoiseSVN handle the same situation?
> I took a look at:
> and I'm aware of the UI issues it mentions. But it seems like:
> - if it's going to revert each selected file individually, it could still
> pass -R when reverting each one, so that if it's a directory, its contents
> will be reverted. This would especially help when you deleted a nested
> directory, and each Revert command just restores one layer of files, but
> not its children.
> - in the dialog, if you select all files in a directory, it could revert
> the directory itself. The UI already makes it look like it will do this, by
> checking the directory when you check its files.
The main issue with reverting a directory is we have to be careful to not
inadvertently revert the children when that is not desired. For example if
you are reverting a property change on a folder, but do not want to revert
the content changes in all files beneath the folder too.
If the folder is scheduled-add, then it should be safe to revert it
recursively since you cannot revert the folder without the children anyway.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
Received on 2016-02-26 22:07:03 CET