Added a comment
This commit is contained in:
parent
f6fee49227
commit
0faf691e63
1 changed files with 14 additions and 0 deletions
|
@ -0,0 +1,14 @@
|
||||||
|
[[!comment format=mdwn
|
||||||
|
username="https://www.google.com/accounts/o8/id?id=AItOawmUJBh1lYmvfCCiGr3yrdx-QhuLCSRnU5c"
|
||||||
|
nickname="Justin"
|
||||||
|
subject="comment 2"
|
||||||
|
date="2013-05-13T17:53:06Z"
|
||||||
|
content="""
|
||||||
|
Be that as it may, the whole reason git-annex exists is to work around fundamental limitations of git!
|
||||||
|
|
||||||
|
The issue is that I don't want to treat a folder which I happen to have applied version control to differently than a folder which happens not to be version controlled (aside from committing to the version-controlled folder, of course!). Both folders are in my git annex; I shouldn't have to worry about it. (My whole \"documents\" folder is in git annex, and it contains many small git repositories.)
|
||||||
|
|
||||||
|
I guess I could write a script to unbundle and re-bundle on command. In fact, one could imagine integrating these scripts into git annex somehow.
|
||||||
|
|
||||||
|
Is that something you'd consider taking upstream?
|
||||||
|
"""]]
|
Loading…
Add table
Add a link
Reference in a new issue