further comment
This commit is contained in:
parent
9127fe4821
commit
3c8f0d1e1b
1 changed files with 14 additions and 0 deletions
|
@ -0,0 +1,14 @@
|
||||||
|
[[!comment format=mdwn
|
||||||
|
username="joey"
|
||||||
|
subject="""comment 2"""
|
||||||
|
date="2018-11-19T19:40:59Z"
|
||||||
|
content="""
|
||||||
|
TBH, an exported tree can contain the same content in two files,
|
||||||
|
and the export database does contain information to deal with that;
|
||||||
|
the location log doesn't really need to be modified to support this.
|
||||||
|
|
||||||
|
Another way to look at it is that you want to build a larger tree, that
|
||||||
|
contains two or more trees in subdirectories, and export the larger tree
|
||||||
|
to the top of the remote. And if you look at this that way, it's
|
||||||
|
already possible to do what you want using only git commands like `git mktree`.
|
||||||
|
"""]]
|
Loading…
Add table
Add a link
Reference in a new issue