
* Fix minor FD leak in journal code. Closes: #754608 * direct: Fix handling of case where a work tree subdirectory cannot be written to due to permissions. * migrate: Avoid re-checksumming when migrating from hashE to hash backend. * uninit: Avoid failing final removal in some direct mode repositories due to file modes. * S3: Deal with AWS ACL configurations that do not allow creating or checking the location of a bucket, but only reading and writing content to it. * resolvemerge: New plumbing command that runs the automatic merge conflict resolver. * Deal with change in git 2.0 that made indirect mode merge conflict resolution leave behind old files. * sync: Fix git sync with local git remotes even when they don't have an annex.uuid set. (The assistant already did so.) * Set gcrypt-publish-participants when setting up a gcrypt repository, to avoid unncessary passphrase prompts. This is a security/usability tradeoff. To avoid exposing the gpg key ids who can decrypt the repository, users can unset gcrypt-publish-participants. * Install nautilus hooks even when ~/.local/share/nautilus/ does not yet exist, since it is not automatically created for Gnome 3 users. * Windows: Move .vbs files out of git\bin, to avoid that being in the PATH, which caused some weird breakage. (Thanks, divB) * Windows: Fix locking issue that prevented the webapp starting (since 5.20140707). # imported from the archive
57 lines
1.9 KiB
Text
57 lines
1.9 KiB
Text
[[!comment format=mdwn
|
|
username="https://www.google.com/accounts/o8/id?id=AItOawm5iosFbL2By7UFeViqkc6v-hoAtqILeDA"
|
|
nickname="Laszlo"
|
|
subject="Definite improvement"
|
|
date="2013-05-03T06:27:12Z"
|
|
content="""
|
|
Hi,
|
|
|
|
I have just tried it out again with the latest (20130501) version.
|
|
|
|
It is really nice to see you have been working on it, and it have improved tremendously!
|
|
The logging issue solved, and logrotates even, and it finished importing without crashing!
|
|
|
|
Remaining polishing things:
|
|
|
|
a)
|
|
The import time is not as good (as you write), it slowes itself down.
|
|
It is true the first 10000 files import in about an hour, but it finishes with everything
|
|
in 9 hours 20 minutes.
|
|
(on a normal laptop, the last 5000 file portion took more then 2 hours)
|
|
|
|
b)
|
|
Every startup means rechecksuming everything, so it means the second start took also around 8-12 hours.
|
|
(I don't know exactly because it finished somewhere during the night, but it was longer then 8 hours)
|
|
I don't think rechecksuming is necessary at all, if the filename, size and date have not modified,
|
|
then why rechecksuming (sha) it?
|
|
|
|
|
|
c)
|
|
It is leaking.
|
|
At the second startup, it reported it successfully added:
|
|
Added 2375 files 5 files probe25366.txt
|
|
|
|
I have not touched the directory. ls confirms leaking:
|
|
|
|
After first start (importing):
|
|
annex_many/.git$ ls -lR |wc -l
|
|
770199
|
|
|
|
After second startup:
|
|
annex_many/.git$ ls -lR |wc -l
|
|
788351
|
|
|
|
d) Without ulimit raise, it does not work at all.
|
|
I think it could be solved by not watching each and every directory all the time.
|
|
Every users will likely have a working directory and some which he don't intend to touch/modify at all.
|
|
Some usecases: photo archiving, video archiving, finished work archiving, etc
|
|
|
|
All the above results with the stress test script.
|
|
I would love to have a confirmation by a thirdparty.
|
|
|
|
Overall I'm impressed with the work you have done.
|
|
|
|
Best,
|
|
Laszlo
|
|
|
|
"""]]
|