mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

import: --message/-m option

Browse source
This commit is contained in:
Joey Hess 2024-01-18 12:41:44 -04:00
parent 162c772703
commit e765d3e24c
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
6 changed files with 45 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

BIN
doc/bugs/Request_the_ability_to_specify_pull_commit_message/.comment_1_6d581ea36afab3829cd56d6d6b83c6f3._comment.swp Normal file
View file

Binary file not shown.

23
doc/bugs/Request_the_ability_to_specify_pull_commit_message/comment_1_6d581ea36afab3829cd56d6d6b83c6f3._comment Normal file
View file

@ -0,0 +1,23 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2024-01-18T16:18:38Z"
content="""
This would need to start with `git-annex import --from=remote`
getting a `--message` option. Which I've just implemented.
As for adding an option to `git-annex pull`, it would need to be an option
other than `--message`, because `git-annex sync` already uses `--message`
for the commit message. And since `git-annex pull` can pull from more than
one remote at a time, it seems that it would need an option that specifies
a message plus which remote to use that message for. Or the option
would need to only be used when using `git-annex pull` with a single
specified remote.
That seems like perhaps unncessary complexity, since if you want to import
a tree from a remote and specify a message, you can just use
`git-annex import` with `--message` now.
And then you can run `git-annex pull` to proceed with the rest of what it does.
Good enough?
"""]]