SourceGear Support

[Vault 3.0.2]
If I try to edit a comment for a committed item and simply add a carriage return, the carriage return is turned into a space. However, if I edit the comment for an item in the pending change set, carriage retuurns are handled correctly.

Back in May, I asked if it was possible to fixed a goofed label comment [1]. One of our developers just asked me the same question - he wants to fix a comment in a label. With Vault 3.0.2, can we do that now?

[1] - http://support.sourcegear.com/viewtopic ... el+comment

On a related note: If you still have .csproj as an excluded file type: - Add folder with a .csproj file in it note that .csproj file is (correctly) not checked note properties (ex: 10KB, 4 files, 1 folder) - check the .csproj checkbox in the file list to have it added too note the properties in the ...

It sounds like Vault isn't picking up the file edits and creating a pending change set item for your files.

Right, but Vault is correctly setting the status of the file as 'edited' in the Client GUI. One part of the Vault client knows the file is edited, but the other doesn't.

I have edited 2 files in my IDE (.cpp and .rc). I look in the Vault client and see both files correctly have the edited status - but only the .cpp is listed in the pending change set. If right click on the .rc and select 'check in...' - nothing happens except a screen redraw. :shock: If right click ...

One of our developers branched a project, changed a couple of files, and was surprised to see that all of the files were shown as modified while browsing them in explorer. However, I just checked this out in Perforce and they do the same thing, so I'm guessing this is probably a common practice amon...

When a branch is created (copy branch), all of the files in the newly created branch have their modified dates set to the date/time that the branch is created. Why is that? We were expecting explorer like semantics: copy a file and the created date changes but not the modified date (until it actuall...

Thanks - taking out /ro2 makes it much more useful now

If I do a diff between a local (edited - non read-only) file and the last version in the repository, DiffMerge treats both as read-only. Why is my local file treated as read-only when it is not

Vault 2.0.3 can be upgraded from any previous release without having to uninstall the previous version.

Does this apply to all vault products, not just the server?:
- client GUI
- admin tool
- VSS import tool

We are currently at 2.0.2

GregM wrote:From the details screen for the label, clear the text from the label field. It will ask you if you're sure, and then delete the label.

Wow , I don't know how that one escaped me all this time. Thanks for mentioning that

The deleting of labels is a bit tricky though, since a lot of folks will label and build every 15 minutes or so, but only want to keep the labels for important builds. They would need a way to easily remove the excess labels - especially for builds that didn't work, or didn't pass smoketests, etc. ...

Great! Man, I've been all over those options and I still missed it

We just made a modification to a file but the file didn't make it into the Pending Change Set. My co-worker first set the refresh interval to 1 minute, with no luck. The he discovered Refresh (F5) which also didn't work. Restarting the Vault client did work. I wish I could be more helpful, but this ...

I don't know if you all picked up that last reply - probably should have been a separate topic. Were you able to reproduce the above described behavior?