add
This commit is contained in:
parent
24a256d402
commit
10b63050eb
2 changed files with 23 additions and 0 deletions
|
@ -0,0 +1,11 @@
|
||||||
|
[[!comment format=mdwn
|
||||||
|
username="joey"
|
||||||
|
subject="""comment 3"""
|
||||||
|
date="2019-09-17T15:50:39Z"
|
||||||
|
content="""
|
||||||
|
Goood thought about assume-unchanged or skip-worktree, that seems likely to
|
||||||
|
work.
|
||||||
|
|
||||||
|
Using git-replace scares me, seems very likely to have unintended
|
||||||
|
consequences.
|
||||||
|
"""]]
|
|
@ -0,0 +1,12 @@
|
||||||
|
[[!comment format=mdwn
|
||||||
|
username="joey"
|
||||||
|
subject="""comment 4"""
|
||||||
|
date="2019-09-17T15:51:21Z"
|
||||||
|
content="""
|
||||||
|
Note that direct mode used to behave this way, with broken symlinks to
|
||||||
|
missing objects. But only on filesystems supporting symlinks, and direct
|
||||||
|
mode was mostly for filesystems w/o that (as well as used by the assistant
|
||||||
|
to let users edit arbitrary file contents w/o bothering with unlocking).
|
||||||
|
|
||||||
|
So, I don't consider v7 not having this yet to be a big regression from v5.
|
||||||
|
"""]]
|
Loading…
Add table
Add a link
Reference in a new issue