git-annex (5.20131127) unstable; urgency=low
* webapp: Detect when upgrades are available, and upgrade if the user
desires.
(Only when git-annex is installed using the prebuilt binaries
from git-annex upstream, not from eg Debian.)
* assistant: Detect when the git-annex binary is modified or replaced,
and either prompt the user to restart the program, or automatically
restart it.
* annex.autoupgrade configures both the above upgrade behaviors.
* Added support for quvi 0.9. Slightly suboptimal due to limitations in its
interface compared with the old version.
* Bug fix: annex.version did not get set on automatic upgrade to v5 direct
mode repo, so the upgrade was performed repeatedly, slowing commands down.
* webapp: Fix bug that broke switching between local repositories
that use the new guarded direct mode.
* Android: Fix stripping of the git-annex binary.
* Android: Make terminal app show git-annex version number.
* Android: Re-enable XMPP support.
* reinject: Allow to be used in direct mode.
* Futher improvements to git repo repair. Has now been tested in tens
of thousands of intentionally damaged repos, and successfully
repaired them all.
* Allow use of --unused in bare repository.
# imported from the archive
This commit is contained in:
Joey Hess
commit
7189dfd77d
6383 changed files with 204042 additions and 0 deletions
|
|
@ -0,0 +1,12 @@
|
|||
[[!comment format=mdwn
|
||||
username="https://www.google.com/accounts/o8/id?id=AItOawmTNrhkVQ26GBLaLD5-zNuEiR8syTj4mI8"
|
||||
nickname="Juan"
|
||||
subject="comment 10"
|
||||
date="2013-08-31T18:20:58Z"
|
||||
content="""
|
||||
I'm already spreading the word. Handling scientific papers, data, simulations and code has been quite a challenge during my academic career. While code was solved long ago, the three first items remained a huge problem.
|
||||
I'm sure many of my colleagues will be happy to use it.
|
||||
Is there any hashtag or twitter account? I've seen that you collected some of my tweets, but I don't know how you did it. Did you search for git-annex?
|
||||
Best,
|
||||
Juan
|
||||
"""]]
|
||||
|
|
@ -0,0 +1,8 @@
|
|||
[[!comment format=mdwn
|
||||
username="http://adamspiers.myopenid.com/"
|
||||
nickname="Adam"
|
||||
subject="Cool"
|
||||
date="2011-12-23T19:16:50Z"
|
||||
content="""
|
||||
Very nice :) Just for reference, here's [my Perl implementation](https://github.com/aspiers/git-config/blob/master/bin/git-annex-finddups). As per [this discussion](http://git-annex.branchable.com/todo/wishlist:_Provide_a___34__git_annex__34___command_that_will_skip_duplicates/#comment-fb15d5829a52cd05bcbd5dc53edaffb2) it would be interesting to benchmark these two approaches and see if one is substantially more efficient than the other w.r.t. CPU and memory usage.
|
||||
"""]]
|
||||
|
|
@ -0,0 +1,8 @@
|
|||
[[!comment format=mdwn
|
||||
username="bremner"
|
||||
ip="156.34.89.108"
|
||||
subject="problems with spaces in filenames"
|
||||
date="2012-09-05T02:12:18Z"
|
||||
content="""
|
||||
note that the sort -k2 doesn't work right for filenames with spaces in them. On the other hand, git-rm doesn't seem to like the escaped names from escaped_file.
|
||||
"""]]
|
||||
39
doc/tips/finding_duplicate_files/comment_3._comment
Normal file
39
doc/tips/finding_duplicate_files/comment_3._comment
Normal file
|
|
@ -0,0 +1,39 @@
|
|||
[[!comment format=mdwn
|
||||
username="mhameed"
|
||||
ip="82.32.202.53"
|
||||
subject="problems with spaces in filenames"
|
||||
date="Wed Sep 5 09:38:56 BST 2012"
|
||||
content="""
|
||||
|
||||
Spaces, and other special chars can make filename handeling ugly.
|
||||
If you don't have a restriction on keeping the exact filenames, then
|
||||
it might be easiest just to get rid of the problematic chars.
|
||||
|
||||
#!/bin/bash
|
||||
|
||||
function process() {
|
||||
dir="$1"
|
||||
echo "processing $dir"
|
||||
pushd $dir >/dev/null 2>&1
|
||||
|
||||
for fileOrDir in *; do
|
||||
nfileOrDir=`echo "$fileOrDir" | sed -e 's/\[//g' -e 's/\]//g' -e 's/ /_/g' -e "s/'//g" `
|
||||
if [ "$fileOrDir" != "$nfileOrDir" ]; then
|
||||
echo renaming $fileOrDir to $nfileOrDir
|
||||
git mv "$fileOrDir" "$nfileOrDir"
|
||||
else
|
||||
echo "skipping $fileOrDir, no need to rename."
|
||||
fi
|
||||
done
|
||||
|
||||
find ./ -mindepth 1 -maxdepth 1 -type d | while read d; do
|
||||
process "$d"
|
||||
done
|
||||
popd >/dev/null 2>&1
|
||||
}
|
||||
|
||||
process .
|
||||
|
||||
Maybe you can run something like this before checking for duplicates.
|
||||
|
||||
"""]]
|
||||
|
|
@ -0,0 +1,8 @@
|
|||
[[!comment format=mdwn
|
||||
username="bremner"
|
||||
ip="156.34.89.108"
|
||||
subject="more about spaces..."
|
||||
date="2012-09-09T19:33:01Z"
|
||||
content="""
|
||||
Ironically, previous renaming to remove spaces, plus some synching is how I ended up with these duplicates. For what it is worth, aspiers perl script worked out for me with a small modification. I just only printed out the duplicates with spaces in them (quoted).
|
||||
"""]]
|
||||
|
|
@ -0,0 +1,8 @@
|
|||
[[!comment format=mdwn
|
||||
username="https://www.google.com/accounts/o8/id?id=AItOawkaBh9VNJ-RZ26wJZ4BEhMN1IlPT-DK6JA"
|
||||
nickname="Alex"
|
||||
subject="printing keys first is the easiest workaround"
|
||||
date="2013-04-01T23:32:23Z"
|
||||
content="""
|
||||
Since the keys are sure to have nos paces in them, putting them first makes working with the output with tools like sort, uniq, and awk simpler.
|
||||
"""]]
|
||||
|
|
@ -0,0 +1,16 @@
|
|||
[[!comment format=mdwn
|
||||
username="https://www.google.com/accounts/o8/id?id=AItOawnkBYpLu_NOj7Uq0-acvLgWhxF8AUEIJbo"
|
||||
nickname="Chris"
|
||||
subject="Find files by key"
|
||||
date="2013-05-03T04:14:55Z"
|
||||
content="""
|
||||
Is there any simple way to search for files with a given key?
|
||||
|
||||
At the moment, the best I've come up with is this:
|
||||
|
||||
````
|
||||
git annex find --include '*' --format='${key} ${file}' | grep <KEY>
|
||||
````
|
||||
|
||||
where `<KEY>` is the key. This seems like an awfully longwinded approach, but I don't see anything in the docs indicating a simpler way to do it. Am I missing something?
|
||||
"""]]
|
||||
|
|
@ -0,0 +1,10 @@
|
|||
[[!comment format=mdwn
|
||||
username="http://joeyh.name/"
|
||||
nickname="joey"
|
||||
subject="comment 7"
|
||||
date="2013-05-13T18:42:14Z"
|
||||
content="""
|
||||
@Chris I guess there's no really easy way because searching for a given key is not something many people need to do.
|
||||
|
||||
However, git does provide a way. Try `git log --stat -S $KEY`
|
||||
"""]]
|
||||
|
|
@ -0,0 +1,10 @@
|
|||
[[!comment format=mdwn
|
||||
username="https://www.google.com/accounts/o8/id?id=AItOawmTNrhkVQ26GBLaLD5-zNuEiR8syTj4mI8"
|
||||
nickname="Juan"
|
||||
subject="This is an awesome feature"
|
||||
date="2013-08-28T13:40:23Z"
|
||||
content="""
|
||||
Thanks. I have quite a lot of papers in PDF formats. Now I'm saving space, have them controlled, synchronized with many devices and found more than 200 duplicates.
|
||||
Is there a way to donate to the project? You really deserve it.
|
||||
Thanks.
|
||||
"""]]
|
||||
|
|
@ -0,0 +1,10 @@
|
|||
[[!comment format=mdwn
|
||||
username="http://joeyh.name/"
|
||||
ip="4.153.8.7"
|
||||
subject="comment 9"
|
||||
date="2013-08-28T20:25:20Z"
|
||||
content="""
|
||||
@Juan the best thing to do is tell people about git-annex, help them use it, and file bug reports. Just generally be part of the git-annex community.
|
||||
|
||||
(If you really want to donate to me, <http://campaign.joeyh.name/> is still open.)
|
||||
"""]]
|
||||
Loading…
Add table
Add a link
Reference in a new issue