File: comment_3_6b579a4f2990a28b33a8170ebd39da5c._comment

package info (click to toggle)
git-annex 10.20250416-2
  • links: PTS, VCS
  • area: main
  • in suites: trixie
  • size: 73,572 kB
  • sloc: haskell: 90,656; javascript: 9,103; sh: 1,469; makefile: 211; perl: 137; ansic: 44
file content (15 lines) | stat: -rw-r--r-- 653 bytes parent folder | download | duplicates (8)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
[[!comment format=mdwn
 username="joey"
 subject="""comment 3"""
 date="2015-10-15T18:46:50Z"
 content="""
This is basically the same as thinking that git should change the SHA1
used to refer to a file in the repository just because it was renamed.
That does not normally make sense.

Including the original extension in the git-annex key is done to avoid
confusing some poorly-behaved programs that expect to follow the symlink
and find a file with an extension. It's best to ignore the extension part
of the key, or if you like, you can change the [[backend|doc/backends]] from SHA256E to
SHA256, and then new keys won't include that extension.
"""]]