mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

formatting

Browse source
This commit is contained in:
https://www.google.com/accounts/o8/id?id=AItOawmGxww5ON3nilm7moGQCWJPnMEdRwNvb7U 2013-10-29 20:25:47 +00:00 • committed by admin
parent 46f6531caa
commit c63bc1a40c
1 changed files with 23 additions and 25 deletions
Download patch file Download diff file Expand all files Collapse all files

18
doc/bugs/git_annex_dead_does_not_work_as_expected_when_multiple_repos_exist_with_the_same_name___40__notably_including_dead_ones__41__.mdwn
View file

@ -6,36 +6,34 @@ I think preferring to mark live repos dead and printing a warning when multiple
### What steps will reproduce the problem? ### What steps will reproduce the problem?
1. Create a new repo /somecopy [[!format sh """
# Create a new repo /somecopy
git clone /central /somecopy git clone /central /somecopy
cd /somecopy cd /somecopy
git annex init somecopy git annex init somecopy
git annex sync git annex sync
cd / cd /
Now, git annex status shows somecopy as an existing repo. # Now, git annex status shows somecopy as an existing repo.
2. Destroy the new repo
# Destroy the new repo
rm -rf /somecopy rm -rf /somecopy
cd /central cd /central
git annex dead somecopy git annex dead somecopy
git annex status correctly hides somecopy, and it is properly dead. # git annex status correctly hides somecopy, and it is properly dead.
3. create it again with the same name, but new UUID
# create it again with the same name, but new UUID
git clone /central /somecopy git clone /central /somecopy
cd /somecopy cd /somecopy
git annex init somecopy git annex init somecopy
git annex sync git annex sync
cd / cd /
4. Destroy the second repo # Destroy the second repo
rm -rf /somecopy rm -rf /somecopy
cd /central cd /central
"""]]
Now, git annex dead somecopy will randomly (based on the order of the UUIDs?) choose to mark dead the already dead old repo or the new repo, in both cases showing success to the user. Now, git annex dead somecopy will randomly (based on the order of the UUIDs?) choose to mark dead the already dead old repo or the new repo, in both cases showing success to the user.