Community
Participate
Working Groups
3.6 I20091020 I'm in a situation where I want to replace several projects with the content of a given branch. I know exactly which projects I want and the tag of the branch. When the branch / version dialog opens I have to first hit the refresh button before I can see the tag I want. Typing the tag without doing the refresh does not give any result. My request is for letting the user type in a tag and hit commit without having to ever do refresh tags since it can be a very long operation.
Szymon what do you think? It sounds reasonable to me.
Makes sense. I will try to fix it in 3.6.
Missed the train. I'll give it another chance in 3.7.
What about if a version/branch of a given tag does not exist? Currently when the window allows choosing only existing tag this problem never occurred. I was expecting in this situation that replace operation would report an error but unfortunately it doesn't. This is because in the first step it lists the resources for update and if the tag does not exist the list of resources is empty. Other operations using this window also don't seem to be prepared that tag may not exists. For instance Compare with -> Branch or version does not display any error but shows that every file in in the project is new. We could check if tag exists in the before the window returns it, but is there a chance that is will be faster than populating the list of tags?
this bug may be related to bug 265025
(In reply to comment #5) > this bug may be related to bug 265025 That is correct, to be consistent a fix we will propose here should be also incorporated into Check Out As wizard.
(In reply to comment #4) > What about if a version/branch of a given tag does not exist? You're right, that's a problematic case we should keep in mind. imo if we decide that a user can type the tag without doing the refresh we should display a warning. Additionally, I would keep that behavior disabled by default, so the user can decide that he wants to work with the dialog that way by switching a preference first.
The API addition has been approved by the PMC.
(In reply to comment #8) > The API addition has been approved by the PMC. Sorry, got the wrong bug.
Moving to 3.8.
We would need some help from the community. Patches are welcome.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. If the bug is still relevant, please remove the "stalebug" whiteboard tag.
