Commit listed for wrong branch

[HankB]

Good morning,
I called up the history of one branch this morning (call it A) and saw that commits I made to branch B were listed in the history for A. I pulled a subsequent copy of B and examined the code to insure that the changes had not been applied there. They had not. I examined the history for B and confirmed that the same commit was listed there as well. I have also made a subsequent commit to B which is not listed in the history for A.

B is originally branched from A (which was originally branched from trunk.) Prior to the commit in question I did merge from A to B (and committed the resulting changes.)

How can we get this sorted out. We need to merge A into B and I'm extremely reluctant to proceed when there seems to be confusion about commits (and when Vault provides no capability to roll back.)

The client identifies itself as SourceGear Vault Professional Version 8.0.1 (30299)

Please advise.

Thanks!

[Beth]

I think I'll need to take a closer look to see what you mean. Could you send an email to support at sourcegear.com (attn: Beth) with a link to this forum thread?

[HankB]

Done - thank you for the quick reply.

... Maybe not:

Delivery to the following recipient failed permanently:

support@sourcegear.com

Technical details of permanent failure:
Message rejected by Google Groups. Please visit http://mail.google.com/support/answer/188131?hl=en to review our Bulk Email Senders Guidelines.

Can you provide the correct email address?

Thanks!

[Beth]

That is the correct email address.

I sent you an email to see if that works. If you receive it, just respond to it and see if that goes through.

HS: 236963

[HankB]

Hi Beth,
I got your email and replied. I got the same response. It looks like I'm getting caught in a spam trap. "Bulk email"

thanks,
hank

[jclausius]

hank,

Looks like this issue was explained in the email sent to support.