Typo fix unncessary -> unnecessary.
Detected while reading recent CHANGELOG entry but then decided to apply to entire codebase and docs since why not?
This commit is contained in:
parent
f091eff476
commit
0151976676
43 changed files with 60 additions and 60 deletions
|
@ -20,7 +20,7 @@ so it re-smudges the work tree file unncessarily.
|
|||
I have not been able to find a number of files to drop that replicates
|
||||
the bug report. When a lot of files are dropped, it starts taking
|
||||
sufficiently long to update the index file that it ends up with a newer
|
||||
timestamp, which avoids the unncessary additional smudging. The worse
|
||||
timestamp, which avoids the unnecessary additional smudging. The worse
|
||||
case I have found here is dropping 9 files causes all 9 to get re-smudged,
|
||||
but that's not enough to get git to use the progress display.
|
||||
"""]]
|
||||
|
|
|
@ -5,7 +5,7 @@
|
|||
content="""
|
||||
Anyway, if git-annex could preserve the mtime of an unlocked file when
|
||||
writing its pointer file or when populating it with content, that would
|
||||
avoid the unncessary smudging. (Which seems better than adding a delay when
|
||||
avoid the unnecessary smudging. (Which seems better than adding a delay when
|
||||
updating the index file, or setting the index's mtime ahead of the current
|
||||
time..)
|
||||
|
||||
|
@ -14,6 +14,6 @@ with annex.thin the content is a hard link and it would probably not be
|
|||
good to change its mtime.
|
||||
|
||||
For now, I didn't do it extensively, but only in depopulatePointerFile.
|
||||
That was enough to eliminate the unncessary smudging after drop that I was
|
||||
That was enough to eliminate the unnecessary smudging after drop that I was
|
||||
seeing.
|
||||
"""]]
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue