comments
This commit is contained in:
parent
53ab91da2a
commit
4bf1690355
3 changed files with 29 additions and 0 deletions
|
@ -3,6 +3,11 @@ possible: `git-annex sync --no-commit --no-pull --no-push --content`.
|
||||||
|
|
||||||
That is a mouthful, so maybe it could be a separate command?
|
That is a mouthful, so maybe it could be a separate command?
|
||||||
|
|
||||||
|
> Actually, that used to sync content with older git-annex at least some
|
||||||
|
> of the time, but [[!commit 2e984c51b65165e79c2fcd5212712ac4e73850de]]
|
||||||
|
> changed/fixed --no-pull and --no-push to also prevent syncing content.
|
||||||
|
> This new command would be the content-syncing part of sync only.
|
||||||
|
|
||||||
Also, such a command could be perhaps be more like `git-annex get/drop/copy`
|
Also, such a command could be perhaps be more like `git-annex get/drop/copy`
|
||||||
in operating on the listed files or current directory and below by default.
|
in operating on the listed files or current directory and below by default.
|
||||||
Although that might make it difficult for it to handle sending files to
|
Although that might make it difficult for it to handle sending files to
|
||||||
|
|
|
@ -0,0 +1,10 @@
|
||||||
|
[[!comment format=mdwn
|
||||||
|
username="joey"
|
||||||
|
subject="""comment 3"""
|
||||||
|
date="2023-06-29T17:49:32Z"
|
||||||
|
content="""
|
||||||
|
@nobodyinperson open another todo for the --recent or similar idea.
|
||||||
|
Something like that would be just another matching option.
|
||||||
|
(However, getting and parsing `git log --since` seems like it would be hard
|
||||||
|
to do efficiently..)
|
||||||
|
"""]]
|
|
@ -0,0 +1,14 @@
|
||||||
|
[[!comment format=mdwn
|
||||||
|
username="joey"
|
||||||
|
subject="""comment 4"""
|
||||||
|
date="2023-06-29T17:51:30Z"
|
||||||
|
content="""
|
||||||
|
@nobodyinperson `git-annex transfer` is not bad. Although I was envisioning
|
||||||
|
this also handling dropping content from repos that don't want it, same as
|
||||||
|
sync does.
|
||||||
|
|
||||||
|
Well, I suppose getting a file from a remote and dropping it from the
|
||||||
|
remote can also be seen as a "transfer". Just because git-annex internally
|
||||||
|
uses "transfer" specifically for copying an object around doesn't mean the
|
||||||
|
command line interface has to.
|
||||||
|
"""]]
|
Loading…
Add table
Add a link
Reference in a new issue