When merging 2 branches, Vault creates a change comment made up of the changeset comments of all of the changes being merged.
However, if this is a long set of comments it is truncated by Vault resulting in lost information.
I'm sure that you'll agree that this is a bad thing.
Can we get it fixed?
Lost Information
Moderator: SourceGear
-
- Posts: 113
- Joined: Wed Sep 26, 2007 3:10 am
- Location: Grantham, Lincs, UK.
- Contact:
Lost Information
Stuart
Using Fortress 2.04 (18845)
Using Fortress 2.04 (18845)
Re: Lost Information
I can log this as a bug.
When you say "long set of comments" how many comments are we talking about?
Is this truncating the number of change set comments, or the comments within change sets?
When you say "long set of comments" how many comments are we talking about?
Is this truncating the number of change set comments, or the comments within change sets?
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
-
- Posts: 113
- Joined: Wed Sep 26, 2007 3:10 am
- Location: Grantham, Lincs, UK.
- Contact:
Re: Lost Information
I noticed it when I was merging branches. The system creates a comment made up of the concatenation of all of the changeset comments used for the branch merge. After doing the merge I looked at one of the files that had been merged and the comments were truncated.
Stuart
Using Fortress 2.04 (18845)
Using Fortress 2.04 (18845)
Re: Lost Information
Thanks for the details. It's been logged.
13636
13636
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager