move wishlist items to todo
This commit is contained in:
Joey Hess
parent
1c8b669f2e
commit
26ce5020d7
12 changed files with 0 additions and 0 deletions
|
|
@ -0,0 +1,5 @@
|
|||
As there's no way to permanently hide remotes and I have to recreate two repos now, I would love to be able to re-use the old UUIDs to remove clutter.
|
||||
|
||||
> git-annex already provides a way to do this: Copy `.git/config` from the
|
||||
> original repo (or use `git-config` to set `annex.uuid`) *before* running
|
||||
> `git annex init`. [[done]] --[[Joey]]
|
||||
17
doc/todo/wishlist:_generic_annex.cost-command.mdwn
Normal file
17
doc/todo/wishlist:_generic_annex.cost-command.mdwn
Normal file
|
|
@ -0,0 +1,17 @@
|
|||
### Current setup
|
||||
|
||||
ATM git-annex has
|
||||
|
||||
remote.<name>.annex-cost
|
||||
remote.<name>.annex-cost-command # command is not provided cmdline options by annex
|
||||
|
||||
to set the cost for a given remote. That requires setting up one of those variables per each host, and possibly hardcoding options for the annex-cost-command providing e.g. the remote name.
|
||||
|
||||
### Suggestion
|
||||
|
||||
wouldn't it be more general and thus more flexible to have a repository-wide
|
||||
|
||||
annex.cost-command
|
||||
|
||||
which could take options %remote, %file and assessed accordingly per each file upon '--get' request to allow maximal flexibility: e.g. some files might better be fetched from remotes supporting transfer compression, some from the web, etc. Also it might be worth providing %remote_kind ("special" vs "git") to disambiguate %remote's?
|
||||
|
||||
|
|
@ -0,0 +1,18 @@
|
|||
### Please describe the problem.
|
||||
|
||||
`git annex reinject` refuses to work while in direct mode.
|
||||
|
||||
When in direct mode git annex reinject could simply perform `rm $symlink; mv $file_copy .; git annex add $file`. I prefer having git annex doing that so I am sure I am not messing up (mistakenly adding new files for instance) and everything is properly managed.
|
||||
|
||||
### What version of git-annex are you using? On what operating system?
|
||||
|
||||
git-annex 4.20130516.1
|
||||
|
||||
~~~~
|
||||
$ lsb_release -a
|
||||
No LSB modules are available.
|
||||
Distributor ID: Ubuntu
|
||||
Description: Ubuntu 12.04.2 LTS
|
||||
Release: 12.04
|
||||
Codename: precise
|
||||
~~~~
|
||||
|
|
@ -0,0 +1,39 @@
|
|||
as of git-annex version 3.20110719, all git-annex commits only contain the word "update" as a commit message. given that the contents of the commit are pretty non-descriptive (SHA1 hashes for file names, uuids for repository names), i suggest to have more descriptive commit messages, as shown here:
|
||||
|
||||
/mnt/usb_disk/photos/2011$ git annex get
|
||||
/mnt/usb_disk/photos/2011$ git show git-annex
|
||||
[...]
|
||||
usb-disk-photos: get 2011
|
||||
|
||||
* 10 files retrieved from 2 sources (9 from local-harddisk, 1 from my-server)
|
||||
* 120 files were already present
|
||||
* 2 files could not be retrieved
|
||||
/mnt/usb_disk/photos/2011$ cd ~/photos/2011/07
|
||||
~/photos/2011/07$ git copy --to my-server
|
||||
~/photos/2011/07$ git show git-annex
|
||||
[...]
|
||||
local-harddisk: copy 2011/07 to my-server
|
||||
|
||||
* 20 files pushed
|
||||
~/photos/2011/07$
|
||||
|
||||
in my opinion, the messages should at least contain
|
||||
|
||||
* what command was used
|
||||
* in which repository they were executed
|
||||
* which files or directories they affected (not necessarily all files, but what was given on command line or implicitly from the working directory)
|
||||
|
||||
--[[chrysn]]
|
||||
|
||||
> The implementation of the git-annex branch precludes more descriptive
|
||||
> commit messages, since a single commit can include changes that were
|
||||
> previously staged to the branch's index file, or spooled to its journal
|
||||
> by other git-annex commands (either concurrently running or
|
||||
> interrupted commands, or even changes needed to automatically merge
|
||||
> other git-annex branches).
|
||||
>
|
||||
> It would be possible to make it *less* verbose, with an empty commit
|
||||
> message. :) --[[Joey]]
|
||||
|
||||
>> Closing as this is literally impossible to do without making
|
||||
>> git-annex worse. [[done]] --[[Joey]]
|
||||
|
|
@ -0,0 +1,37 @@
|
|||
It would be nice if the 'unused' command could optionally display info about the actual files behind its cryptic keys.
|
||||
|
||||
I created a (very rough) bash script that simply splices in some info from git log -S'KEY' --numstat into the unused list, like so:
|
||||
|
||||
arand@mas:~/annex(master)$ bash ~/utv/scripts/annex-vunused
|
||||
unused . (checking for unused data...) (checking master...) (checking synced/master...) (checking origin/HEAD...) (checking seagate/master...)
|
||||
Some annexed data is no longer used by any files:
|
||||
NUMBER KEY
|
||||
1 SHA256E-s1073741824--49bc20df15e412a64472421e13fe86ff1c5165e18b2afccf160d4dc19fe68a14.img
|
||||
8f479a4 Sat Feb 23 16:14:12 2013 +0100 remove bigfile
|
||||
0 1 dummy_bigfile.img
|
||||
2988d18 Sat Feb 23 16:13:48 2013 +0100 dummy file
|
||||
1 0 dummy_bigfile.img
|
||||
(To see where data was previously used, try: git log --stat -S'KEY')To remove unwanted data: git-annex dropunused NUMBER
|
||||
ok
|
||||
The script:
|
||||
|
||||
#!/bin/bash
|
||||
|
||||
pipe="$(mktemp -u)"
|
||||
mkfifo "$pipe"
|
||||
|
||||
git annex unused >"$pipe" || exit 1 &
|
||||
|
||||
while read -r line
|
||||
do
|
||||
key="$(echo "$line" | sed 's/^[^-]*-\([^-]*\)-.*/\1/')"
|
||||
echo -n "$line"
|
||||
test -n "$key" && \
|
||||
echo && \
|
||||
git log --format="%h %cd %s" --numstat -S"$key" | \
|
||||
sed '/^$/d;/git-annex automatic sync/,/^ /d;s/^/\t\t/'
|
||||
|
||||
done < "$pipe"
|
||||
rm "$pipe"
|
||||
|
||||
It would be nice if something like this was available as an option, since it's good way to get a quick overview of what the content is, and if it's safe to drop it.
|
||||
|
|
@ -0,0 +1,4 @@
|
|||
It would be helpful to have a way to query things like a repository's description and trust level, without having to poke in the git-annex branch. For example, "git annex describe ." currently clears the description but could print the current one instead.
|
||||
|
||||
> `git annex status` now breaks down the repository list by type. [[done]]
|
||||
> --[[Joey]]
|
||||
|
|
@ -0,0 +1,10 @@
|
|||
[[!comment format=mdwn
|
||||
username="http://joey.kitenet.net/"
|
||||
nickname="joey"
|
||||
subject="comment 1"
|
||||
date="2011-10-27T17:09:33Z"
|
||||
content="""
|
||||
`git annex describe` only sets the description to avoid complication. Imagine using it in a script for example.
|
||||
|
||||
`git annex status` shows the description. It does not show the trust level because I have not thought of a visually pleasing and compact way to show it in the repository list there.. suggestions appreciated, since the same list is used by `whereis`, and showing trust levels there would be particularly useful.
|
||||
"""]]
|
||||
|
|
@ -0,0 +1,32 @@
|
|||
[[!comment format=mdwn
|
||||
username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
|
||||
nickname="Richard"
|
||||
subject="comment 2"
|
||||
date="2011-10-29T18:28:13Z"
|
||||
content="""
|
||||
Possible solutions:
|
||||
|
||||
This:
|
||||
|
||||
trusted repositories:
|
||||
UUID -- foo
|
||||
semi-trusted repositories:
|
||||
UUID -- bar
|
||||
untrusted repositories:
|
||||
UUID -- baz
|
||||
|
||||
or this:
|
||||
|
||||
UUID -- trusted -- foo
|
||||
UUID -- semi-trusted -- bar
|
||||
UUID -- untrusted -- baz
|
||||
|
||||
or this:
|
||||
|
||||
known repositories (!/*/X):
|
||||
UUID -- ! foo
|
||||
UUID -- * bar
|
||||
UUID -- X baz
|
||||
|
||||
If you want to reformat this output, putting 'here', 'origin', etc into fixed formatting might make sense, as well. -- Richard
|
||||
"""]]
|
||||
36
doc/todo/wishlist:_simple_url_for_webapp.mdwn
Normal file
36
doc/todo/wishlist:_simple_url_for_webapp.mdwn
Normal file
|
|
@ -0,0 +1,36 @@
|
|||
### Please describe the problem.
|
||||
|
||||
The environment is os/x with chrome as the browser.
|
||||
|
||||
Let's say I close the tab with the webapp running in it. The 'git-annex webapp' process is still running, according to 'ps'.
|
||||
|
||||
So I open a new tab, but then what do I type into the browser url bar to get the app back? What is usually there is a loopback address and an authorisation hash.
|
||||
|
||||
* Should I double-click on the git-annex icon in the dock (or Applications directory)?
|
||||
* I figured out from observing the startup that if I give the url ://localhost/Users/me/annex/.git/annex/webapp.html I will get redirected to the right place.
|
||||
Should I set up a bookmark for that?
|
||||
|
||||
### What steps will reproduce the problem?
|
||||
|
||||
see above.
|
||||
|
||||
### What version of git-annex are you using? On what operating system?
|
||||
|
||||
Version: 4.20130723-ge023649
|
||||
Build flags: Assistant Webapp Pairing Testsuite S3 WebDAV FsEvents XMPP DNS
|
||||
os: os/x 10.8.4
|
||||
|
||||
### Please provide any additional information below.
|
||||
|
||||
I notice that in the webapp ui, all the items at the top of the page highlight when one hovers over them and have useful URLs attached,
|
||||
with the exception of the 'git-annex' item at the far left.What if that had the entry point url attached to it (so one could bookmark that)?
|
||||
|
||||
> The git-annex assistant is designed to stay running in the background whether you have the web browser open or not. You can open the web display at any time by
|
||||
> using the git-annex menu item (on linux) or running the git-annex-webapp
|
||||
> program (which is in the DMG on OSX).
|
||||
>
|
||||
> If the file:// url were exposed to users, it would not work if
|
||||
> the assistant had not already been started. This is why there is a program
|
||||
> to open the webapp, not an url.
|
||||
>
|
||||
> Not a bug; [[done]] --[[Joey]]
|
||||
|
|
@ -0,0 +1,10 @@
|
|||
[[!comment format=mdwn
|
||||
username="https://www.google.com/accounts/o8/id?id=AItOawkfHTPsiAcHEEN7Xl7WxiZmYq-vX7azxFY"
|
||||
nickname="Vincent"
|
||||
subject="comment 1"
|
||||
date="2013-07-24T14:46:22Z"
|
||||
content="""
|
||||
typo
|
||||
|
||||
url should be - file://localhost/Users/me/annex/.git/annex/webapp.html
|
||||
"""]]
|
||||
|
|
@ -0,0 +1,18 @@
|
|||
Currently there is no way to drop files, or list what files are available, on a special remote.
|
||||
It would be good if "git annex drop" and "git annex find" supported the --from argument.
|
||||
|
||||
> I agree, drop should support --from.
|
||||
>> [[done]] --[[Joey]]
|
||||
>
|
||||
> To find files *believed* to be present in a given remote, use
|
||||
> `git annex find --in remote`
|
||||
> Note that it might show out of date info, since it does not actually go
|
||||
> check the current contents of the remote. The only reason to support
|
||||
> `find --from` would be to always check, but I don't think that's needed.
|
||||
> --[[Joey]]
|
||||
|
||||
For commands that don't support the --from argument, it would also be nice to print an error.
|
||||
Currently running "git annex drop --from usbdrive" doesn't behave as hoped and instead drops
|
||||
all content from the local annex.
|
||||
|
||||
> This is done now. --[[Joey]]
|
||||
|
|
@ -0,0 +1,8 @@
|
|||
[[!comment format=mdwn
|
||||
username="http://joey.kitenet.net/"
|
||||
nickname="joey"
|
||||
subject="comment 1"
|
||||
date="2011-10-27T17:13:43Z"
|
||||
content="""
|
||||
Well, I don't think you mean \"special remotes\", but just any old remote (special or not).
|
||||
"""]]
|
||||
Loading…
Add table
Add a link
Reference in a new issue