moved all wishlist stuff out of the forum; and closed a bunch of themmoved
all wishlist stuff out of the forum; and closed a bunch of themmoved all wishlist stuff out of the forum; and closed a bunch of themmoved all wishlist stuff out of the forum; and closed a bunch of themmoved all wishlist stuff out of the forum; and closed a bunch of themmoved all wishlist stuff out of the forum; and closed a bunch of themmoved all wishlist stuff out of the forum; and closed a bunch of themmoved all wishlist stuff out of the forum; and closed a bunch of themmoved all wishlist stuff out of the forum; and closed a bunch of them
This commit is contained in:
parent
e7da1dfd29
commit
dc19b2398d
46 changed files with 14 additions and 1 deletions
|
@ -0,0 +1,17 @@
|
|||
[[!comment format=mdwn
|
||||
username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
|
||||
nickname="Richard"
|
||||
subject="comment 1"
|
||||
date="2011-04-17T23:46:37Z"
|
||||
content="""
|
||||
--to and --from seem to have different semantics than --source and --destination. Subtle, but still different.
|
||||
|
||||
That being said, I am not sure --from and --to are needed at all. Calling the local repo . and all remotes by their name, they are arguably redundant and removing them would make the syntax a lot prettier; mv and cp don't need them, either.
|
||||
|
||||
I am not sure changing syntax at this point is considered good style though personally, I wouldn't mind adapting and would actually prefer it over using --to and --from.
|
||||
|
||||
-v and -q would be nice.
|
||||
|
||||
|
||||
Richard
|
||||
"""]]
|
|
@ -0,0 +1,19 @@
|
|||
[[!comment format=mdwn
|
||||
username="http://joey.kitenet.net/"
|
||||
nickname="joey"
|
||||
subject="comment 2"
|
||||
date="2011-04-19T20:13:10Z"
|
||||
content="""
|
||||
Let's see..
|
||||
|
||||
* -v is already an alias for --verbose
|
||||
|
||||
* I don't find --source and --destination as easy to type or as clear as --from or --to.
|
||||
|
||||
* -F is fast, so it cannot be used for --force. And I have no desire to make it easy to mistype a short option and enable --force; it can lose data.
|
||||
|
||||
@richard while it would be possible to support some syntax like \"git annex copy . remote\"; what is it supposed to do if there are local files named foo and bar, and a remotes named foo and bar? Does \"git annex copy foo bar\" copy file foo to remote bar, or file bar from remote foo? I chose to use --from/--to to specify remotes independant of files to avoid such
|
||||
ambiguity, which plain old `cp` doesn't have since it's operating entirely on filesystem objects, not both filesystem objects and abstract remotes.
|
||||
|
||||
Seems like nothing to do here. [[done]] --[[Joey]]
|
||||
"""]]
|
|
@ -0,0 +1,8 @@
|
|||
[[!comment format=mdwn
|
||||
username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
|
||||
nickname="Richard"
|
||||
subject="comment 3"
|
||||
date="2011-04-20T21:28:06Z"
|
||||
content="""
|
||||
Good point. scp fixes this by using a colon, but as colons aren't needed in git-annex remotes' names... -- RichiH
|
||||
"""]]
|
Loading…
Add table
Add a link
Reference in a new issue