6.0 CVS commit dialog: Any way to use the one in 5?

Is there a flag somewhere that will allow me to use the old CVS commit dialog? I couldn't find anything in the version control settings.

14 comments

Hello Will,

W> Is there a flag somewhere that will allow me to use the old CVS
W> commit dialog? I couldn't find anything in the version control
W> settings.

No.

--
Dmitry Jemerov
Software Developer
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"


0

Hello Will,

W> Is there a flag somewhere that will allow me to use the old CVS
W> commit dialog? I couldn't find anything in the version control
W> settings.

Why exactly do you want to use the old dialog?

--
Dmitry Jemerov
Software Developer
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"


0

I can tell you why I would like to use the old version sometimes.

When I tell idea to commit one file, I expect it to commit that file. I don't expect to wait 5-10 seconds waiting for synchronization. V5 was immediate. V6 disrupts my ability to do anything else in idea.

Also, whenever I'm checking in more than 10 files, V6 fails to check them in one pass, I have to tell it to commit 2-4 times. Again frustrating.

Don't get me wrong, I love the idea behind the VCS support in V6, it's the implementation that frustrates me.

Thanks,

Greg

0

Very often I only want to commit a few of the changed files. When I go to commit for the second time, I like to have all the changed files in front of me, with the selected/deselected values saved.

When I move the uncommitted files to a new changelist, they're not in front of my face the next time I commit and sometimes I forget there is a file that needs to be included. I don't like looking in two places.

Less importantly, I find all the checkboxes much more difficult to look at. I was a fan of the strike-through/grayed-out line items--It was much easier to see at a glance which files were going to be included.

I'm sure the multiple change lists have their uses, but I would love the option to switch to the old style.

0

Hello Greg,

g> I can tell you why I would like to use the old version sometimes.
g>
g> When I tell idea to commit one file, I expect it to commit that file.
g> I don't expect to wait 5-10 seconds waiting for synchronization. V5
g> was immediate. V6 disrupts my ability to do anything else in idea.

What VCS are you using? Could you please take a CPU snapshot of the synchronization
process? We definitely don't see the synchronization taking 5-10 seconds
on every commit here.

g> Also, whenever I'm checking in more than 10 files, V6 fails to check
g> them in one pass, I have to tell it to commit 2-4 times. Again
g> frustrating.

What exactly fails, and how?

--
Dmitry Jemerov
Software Developer
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"


0

Hello Will,

W> Very often I only want to commit a few of the changed files. When I
W> go to commit for the second time, I like to have all the
W> changed files in front of me, with the selected/deselected values
W> saved.
W>
W> When I move the uncommitted files to a new changelist, they're not in
W> front of my face the next time I commit and sometimes I forget there
W> is a file that needs to be included. I don't like looking in two
W> places.

There is a single place where you can look to see this information, and it's
called the Changes view. Have you tried using it?

W> Less importantly, I find all the checkboxes much more difficult to
W> look at. I was a fan of the strike-through/grayed-out line items--It
W> was much easier to see at a glance which files were going to be
W> included.

It's certainly easy to show additional strike-through decoration on unchecked
items. Do others think it would be useful?

--
Dmitry Jemerov
Software Developer
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"


0

+1

It's certainly easy to show additional strike-through decoration on
unchecked items. Do others think it would be useful?



0

Hello Greg,

g> I can tell you why I would like to use the old
version sometimes.
g>
g> When I tell idea to commit one file, I expect it
to commit that file.
g> I don't expect to wait 5-10 seconds waiting for
synchronization. V5
g> was immediate. V6 disrupts my ability to do
anything else in idea.

What VCS are you using? Could you please take a CPU
snapshot of the synchronization
process? We definitely don't see the synchronization
taking 5-10 seconds
on every commit here.


Unfortunately, I'm using an older version of VSS, version 6.0c
There are two specific issues I'm having.
1 - Checking in just a single file. I choose the menu option to checking a single file, and Idea pops up a dialog saying "Finish VCS Refresh". It takes 5-10 seconds for this to go away and then Idea shows me the "Commit Changes" dialog. The cpu is barely working during this time, 10-40% utilization.
My issue with this is that I selected to check in a single file. That is what I want Idea to do. It was fast and simple in 5.0. Now Idea 6.0 second guesses what I want to do, instead of doing what I explicitly asked.

2 - Next Issue. Idea hangs on checking out a file. This rarely happens in 5.0, maybe once a month, and there were always network issues to blame. Now, Idea locks up 2-3 times a day. I wait a period of time (up to a minute) and then kill the idea process & have to restart. While I'm waiting for Idea to restart, I can open the VSS client and check files in and out at will. This issue may cause me to revert to 5.0. It is just too much of a concentration breaker.
It is slightly disturbing that Idea feels like a single threaded app while doing this. I want to be able to continue working while it tries to check out the file.

g> Also, whenever I'm checking in more than 10 files,
V6 fails to check
g> them in one pass, I have to tell it to commit 2-4
times. Again
g> frustrating.

What exactly fails, and how?

By fails, I mean that if I start with 24 files in my change list (a combo of new & changed) after the first commit, I might have 17 files in the change list. After the second commit, it may have committed all of them, or I might have 5 left. It feels very random & I'm never quite sure when the process is complete. Is it the small red square? Is it the (updating...) text?
This may be user error, I just don't know when it is complete

Thanks for the response, I do love everything else about V6, especially emma integration.

Greg

0

It's certainly easy to show additional strike-through
decoration on unchecked
items. Do others think it would be useful?


Yes, please add this decoration!!

0

The Changes view isn't the last thing I see before I commit; it's in a separate place. I like to go through evert file and see if there is one excluded that should be included right beforehand.

I think the crux of my issue is these two facts:

1) Apart from creating a new change list, the commit dialog does not remember what was selected and deselected from commit to commit (it used to).

2) The gray strike through is much clearer than a list of checkboxes.

0

If you use a product like process explorer you can see under Idea process
a vss.exe process that hangs idea, killing that process will make Idea complete
the checkout.
From build 6077 ( 6.0.2 EAP) the problem seem occurs only on the first vss
operation after project changing and the vss integration is more stable.

Ciao,

Roberto

>> Hello Greg,
>>
>> g> I can tell you why I would like to use the old
>> version sometimes.
>> g>
>> g> When I tell idea to commit one file, I expect it
>> to commit that file.
>> g> I don't expect to wait 5-10 seconds waiting for
>> synchronization. V5
>> g> was immediate. V6 disrupts my ability to do
>> anything else in idea.
>> What VCS are you using? Could you please take a CPU
>> snapshot of the synchronization
>> process? We definitely don't see the synchronization
>> taking 5-10 seconds
>> on every commit here.

Unfortunately, I'm using an older version of VSS, version 6.0c

There are two specific issues I'm having.

1 - Checking in just a single file. I choose the menu option to
checking a single file, and Idea pops up a dialog saying "Finish VCS
Refresh". It takes 5-10 seconds for this to go away and then Idea
shows me the "Commit Changes" dialog. The cpu is barely working
during this time, 10-40% utilization.

My issue with this is that I selected to check in a single file. That
is what I want Idea to do. It was fast and simple in 5.0. Now Idea
6.0 second guesses what I want to do, instead of doing what I
explicitly asked.

2 - Next Issue. Idea hangs on checking out a file. This rarely
happens in 5.0, maybe once a month, and there were always network
issues to blame. Now, Idea locks up 2-3 times a day. I wait a period
of time (up to a minute) and then kill the idea process & have to
restart. While I'm waiting for Idea to restart, I can open the VSS
client and check files in and out at will. This issue may cause me to
revert to 5.0. It is just too much of a concentration breaker. It is
slightly disturbing that Idea feels like a single threaded app while
doing this. I want to be able to continue working while it tries to
check out the file.

>> g> Also, whenever I'm checking in more than 10 files,
>> V6 fails to check
>> g> them in one pass, I have to tell it to commit 2-4
>> times. Again
>> g> frustrating.
>> What exactly fails, and how?
>>

By fails, I mean that if I start with 24 files in my change list (a
combo of new & changed) after the first commit, I might have 17 files
in the change list. After the second commit, it may have committed
all of them, or I might have 5 left. It feels very random & I'm never
quite sure when the process is complete. Is it the small red square?
Is it the (updating...) text?

This may be user error, I just don't know when it is complete

Thanks for the response, I do love everything else about V6,
especially emma integration.

Greg



0

Hello Greg,

>> What VCS are you using? Could you please take a CPU
>> snapshot of the synchronization
>> process? We definitely don't see the synchronization
>> taking 5-10 seconds
>> on every commit here.
g> Unfortunately, I'm using an older version of VSS, version 6.0c

Many VSS fixes are included in the latest EAP build for 6.0.2, build 6083.
You can download it from:
http://www.jetbrains.net/confluence/display/IDEADEV/6.0.2+EAP

Please report if it makes your experience better (or not :) ).

--
Dmitry Jemerov
Software Developer
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"


0

Hi Dmitry,

Thanks for the upgrade advice. Build 6083 has not hung up on me at all. Also, I now see error messages when something fails (which explains the mysterious not checking everything in.
I even had 500+ files all checked in/added in a few seconds. Nice job :)

Now, to get these guys off VSS...

Greg

0

Please sign in to leave a comment.