Settings and activity
133 results found
-
6 votes
Göran Wallgren
supported this idea
·
-
10 votesGöran Wallgren
supported this idea
·
-
7 votesGöran Wallgren
supported this idea
·
-
7 votesGöran Wallgren
supported this idea
·
-
9 votesGöran Wallgren
supported this idea
·
-
13 votesGöran Wallgren
supported this idea
·
-
23 votesGöran Wallgren
supported this idea
·
-
10 votesGöran Wallgren
supported this idea
·
-
38 votes
Hi supporters!
We would need an answer to the question we asked here to be able to move forward. Otherwise, without extra info, we would need to discard.
Thanks,
pablo
An error occurred while saving the comment Göran Wallgren
supported this idea
·
-
12 votes
An error occurred while saving the comment Göran Wallgren
commented
REPLY: When I said "it has been recommended", I actually meant "recommended by Codice staff" (!) See these recent answers on the forums:
http://www.plasticscm.net/index.php?/topic/2581-update-workspace-with-pending-changes/
http://www.plasticscm.net/index.php?/topic/2901-no-way-to-switch-workspace-to-here-with-changes/
So much for TOTALLY discouraging the use of this setting... ;) There is NO mention of side-effects in these answers!
IMHO, since this setting causes so much potential headscratching, it would be better to remove it and instead unify the Update methods.
It's also very confusing to _not_ have the same behavior whichever way the user chooses to update the workspace. Using method (3) everywhere would also make it much simpler to carry pending changes over to another branch (no need to shelve). In Subversion we could do that as well...
In your answer, what does (also triggered by "2") mean? It would seem to indicate that method (1) and (2) are not fully identical after all, but maybe it means something else?
Göran Wallgren
shared this idea
·
-
6 votesGöran Wallgren
supported this idea
·
-
3 votesGöran Wallgren
shared this idea
·
-
4 votesGöran Wallgren
supported this idea
·
-
3 votesGöran Wallgren
shared this idea
·
-
24 votesGöran Wallgren
supported this idea
·
An error occurred while saving the comment Göran Wallgren
commented
With release .742 a part of this uservoice is implemented, namely the possibility to jump from a selected branch in the Branches view into the Branch Explorer (fixing that other uservoice) :
https://www.plasticscm.com/download/releasenotes/5.4.16.742What remains for this uservoice to be completed is to add support for multi-selected branches and the relevant commands under the "Branch Explorer" sub-menu.
BTW, I want this on Windows and "robl" wants it on gtkplastic. ;)
Finally, as a tip to "robl", similar to the filters for the table view one can add inclusion/exclusion filters in the Branch Explorer as well. These filters can be toggled on/off. (At least on Windows.)
An error occurred while saving the comment Göran Wallgren
commented
An error occurred while saving the comment Göran Wallgren
commented
Actually, this was duplicated by me here: http://plasticscm.uservoice.com/forums/15467-general/suggestions/9588258-branches-view-add-submenu-branch-explorer-for-q
I'll append my comments here, for reference:
Currently, there is no easy way to jump into the Branch Explorer from selected branch(es) in the Branches view.
This would be very convenient since it can sometimes be cumbersome to locate a specific task branch etc in the main Branch Explorer, while it's quick to find it in the excellent "Tree view" of the Branches view.
I'd like to have in the Branches view a (partial?) clone of the "Branch Explorer" submenu from the Branch Explorer view:
* Show selected branches in a new diagram
* Show selected and related branches in a new diagram
* etcAlso, when only one branch is selected I'd like a command to simply switch to the standard branch explorer and focus the "head" changeset.
An error occurred while saving the comment Göran Wallgren
commented
Excellent idea, we want this ASAP! ;)
-
3 votesGöran Wallgren
shared this idea
·
-
11 votes
An error occurred while saving the comment Göran Wallgren
commented
Yes please! You allow non-unique (child) branch names but you don't support finding a branch by full name.
Göran Wallgren
shared this idea
·
-
36 votes
An error occurred while saving the comment Göran Wallgren
commented
UPDATE: It's possible to use the following syntax to check for an attribute-value, regardless of which attribute has that value:
where attrvalue = 'some_name'
It's also possible to combine these with OR to match one of several values:
where attrvalue = 'some_name' or attrvalue = 'other_name'
However, combining these with AND does not work to match two different values of two different attributes.
Also, the following works as expected (note the use of OR between parantheses) :
where (attribute = 'attr1' and attrvalue = 'some_name') or (attribute = 'attr2' and attrvalue = 'other_name')
However, the following does not work as one would want (note the use of AND between parantheses) :
where (attribute = 'attr1' and attrvalue = 'some_name') and (attribute = 'attr2' and attrvalue = 'other_name')
The exact syntax and limitations of the cm find command remains a mystery... It is not very consistent, unfortunately.
An error occurred while saving the comment Göran Wallgren
commented
I added the request for branch depth/level support in "find branch" as a separate uservoice here:
https://plasticscm.uservoice.com/forums/15467-general/suggestions/13071576-add-support-for-branch-depth-in-find-branch-commanAn error occurred while saving the comment Göran Wallgren
commented
I added the request for branch namespace support in "find branch" as a separate uservoice here:
https://plasticscm.uservoice.com/forums/15467-general/suggestions/13071435-add-support-for-namespace-in-find-branch-command
Please vote for it if you care about this...An error occurred while saving the comment Göran Wallgren
commented
UPDATE: The following command actually works (at least in 5.4.16.731) for finding all the branches that do NOT have the specific attribute "branch_status" applied (regardless of whether there are other attributes or not) :
cm find branch where not attribute = 'branch_status'
(Note the use of "not" instead of "!=" in this query...)
An error occurred while saving the comment Göran Wallgren
commented
To filter the Branches view for branches that do NOT have a specific attribute for our "branch_status" attribute, I can use the following syntax:
find branch where attribute="branch_status" and attrvalue != "completed"
However, that will NOT include branches that don't have that attribute applied at all. It would be much more useful if there was a way to include these too in the same query.
To find the branches that don't have the attribute applied, it would be logical to use the following syntax:
find branch where attribute != "branch_status"
That query works, but not as expected. It has a very counter-intuitive interpretation: [where (count attributes > 0) AND (attributes DO NOT CONTAIN 'branch_status')].
Please consider changing the interpretation to simply: [where (attributes DO NOT CONTAIN 'branch_status')].
Additionally, finding a branch by namespace is not possible. Even worse, [find branch where name = 'main'] returns 1 branch, but [find branch where name = '/main'] returns none! Please add full namespace support so we can find branches by complete name such as name = '/main/task001/subtask_1'.
Also, I propose adding a "depth" or "level" filter-option for the branch find-object, to filter on branch namespace-depth (like "Display branch levels" in Branch Explorer).
An error occurred while saving the comment Göran Wallgren
commented
Also, a way to find all branches etc where a specific attribute is NOT applied.
Göran Wallgren
supported this idea
·
-
4 votes
An error occurred while saving the comment Göran Wallgren
commented
"... actually showing whether the changeset is involved on a merge or not, seems to be a good idea."
Thanks! The following uservoices are related to this idea:
It is also discussed in the this forum post: http://www.plasticscm.net/index.php?/topic/1741-merge-not-displayed-neither-in-file-history-nor-in-file-2d-history/
Göran Wallgren
shared this idea
·
-
6 votes
An error occurred while saving the comment Göran Wallgren
commented
Ehrm, so how am I supposed to use grep in the query box in the Branches view inside the Plastic SCM GUI? ;P
Göran Wallgren
shared this idea
·
Make sure to handle the new support for "partial readonly xlinks" well (indicate targeted sub-directory).
For both src and dst, show the target sub-dir, changeset, (branch), repo, (server).