Re: [Subclipse-users] Bug or unexpected behavior when comitting files in non versioned folders

On 1/15/07, Reinhard Brandstaedter <Reinhard.Brandstaedter@jku.at> wrote:
>
> Hi,
>
> I just found something that is - in my opinion - a unexpected behavior
> in subclipse.
>
> Assume I create a new folder in my working copy and in this folder a new
> file. I don't add this file or folder to version control.
> Then I issue a "commit" on the file.
> Subclipse then implicitly creates another transaction and commits the
> parent folder, resulting in two commits with the same message.

Just to summarize, the problem as you see it is that this is done with
multiple transactions? You can file an issue in the issue tracker if you
would like. Any code like this would pre-date my involvement with this
project but it is something that I, or someone else, can look into.

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/