Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Interests
See all
Community resources
Top groups
Explore all groups
Community resources
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Join now to unlock these features and more

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Get started Tell me more
Atlassian Community about banner
4,461,513
Community Members
 
Community Events
176
Community Groups

Sub version Error while commiting

mohan
mohan Jul 04, 2018

 

Hi,

For svn We moved from storage A to storage B. The same was exposed to users only today. I committed files on Monday (02-July-2018). The same was committed in storage A. The back up and restore to the new storage does not have these files. When i try to commit files in new storage, it throws out of sync error,

 

How do i overcome this. Naturally, the version numbers in both the storage will be out of sync.

Answer
Watch
Like Be the first to like this
160 views

0 answers

Suggest an answer

Log in or Sign up to answer
Bamboo
Bamboo
TAGS

Atlassian Community Events

See all events