File Checked Out on One Computer - Undo From Another

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
kwilliams
Posts: 8
Joined: Tue Jun 15, 2004 12:20 pm
Location: Tulsa, OK
Contact:

File Checked Out on One Computer - Undo From Another

Post by kwilliams » Fri Aug 20, 2004 11:19 am

This is probably a stupid question, but I just can't figure it out. I exclusively checked out a file (web.config for an ASP.NET project) on my old computer and now I need to undo that checkout so that I can modify it on my new computer. I no longer have access to the old machine.

How can I force that checkout to be undone?

kwilliams
Posts: 8
Joined: Tue Jun 15, 2004 12:20 pm
Location: Tulsa, OK
Contact:

Post by kwilliams » Fri Aug 20, 2004 11:33 am

Okay, it WAS a stupid question. It's RIGHT THERE in the admin tool. I don't know how I missed that!

George Mills
Posts: 33
Joined: Tue Aug 24, 2004 8:19 am

Post by George Mills » Sun Aug 29, 2004 9:31 pm

We do this frequently in vss :wink: can the user undo the checkout on another machine? We are constantly juggling between instruments and our desktops and end up in this situation.

dan
Posts: 2448
Joined: Wed Dec 17, 2003 5:03 pm
Location: SourceGear
Contact:

Post by dan » Mon Aug 30, 2004 7:12 am

George Mills wrote:We do this frequently in vss :wink: can the user undo the checkout on another machine? We are constantly juggling between instruments and our desktops and end up in this situation.
Not currently (you can only undo a checkout from another user or another machine from the Admin Tool). We do plan to allow a user to undo his or her own checkout from a different machine in a future release.

montek
Posts: 107
Joined: Mon Jan 05, 2004 8:46 am

Post by montek » Sat Oct 16, 2004 5:48 pm

kwilliams wrote:Okay, it WAS a stupid question. It's RIGHT THERE in the admin tool. I don't know how I missed that!
Be careful, though, because if more than one person has it checked out, it will undo EVERYONE'S checkout without warning. (Not expected behavior, IMO.)

Post Reply