blob: 4a3329326b95def0d3d1a153aaca1f529b793ff4 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
|
#### What steps will reproduce the problem?
When moving to direct mode files get flagged in git as 'typechange'.
md test-directmode; cd test-directmode ; git init; git annex init
date > test.file ; git annex add test.file
git commit -m "Initial commit"
git status # All fine
git annex direct
git status # typechange: test.file
git add test.file && git commit -m "looks like I should commit this"
# And the symlink is now broken...
#### What is the expected output? What do you see instead?
Surprised to see the typechange status in git. Would not expect to see anything, however, if you `git add` and then commit you can get data loss. :-(
#### What version of git-annex are you using? On what operating system?
git-annex version: 3.20130114
OS: OSX 10.6.8
#### Please provide any additional information below.
> This was the pre-commit hook, made it not run in direct mode. [[done]]
>
> However, it's normal to see typechanged files in direct mode, and many
> git commands that manipulate files in the working tree *can* result in
> data loss. This is documented on [[direct_mode]].
> --[[Joey]]
|
