Comment moderation
This commit is contained in:
http://joeyh.name/
admin
parent
efadf5215a
commit
8c3491f50c
33 changed files with 461 additions and 0 deletions
|
|
@ -0,0 +1,12 @@
|
|||
[[!comment format=mdwn
|
||||
username="https://www.google.com/accounts/o8/id?id=AItOawlYu7QmD7wrbHWkoxuriaA9XcijM-g5vrQ"
|
||||
nickname="Royal"
|
||||
subject="comment 2"
|
||||
date="2012-06-05T17:19:16Z"
|
||||
content="""
|
||||
Hi,
|
||||
|
||||
I want to replace rsync with aspera-rsync. Whenever there is file transfer between 2 repositories which are in two different hosts, git-annex will use rsync protocol. I am trying to replace that rsync call with aspera-rsync so that transfer can be more faster. Since I am new to Haskell I am finding difficulties to understand the flow of execution. Is there any way I can debug so that I can get the flow?
|
||||
|
||||
Thanks
|
||||
"""]]
|
||||
|
|
@ -0,0 +1,8 @@
|
|||
[[!comment format=mdwn
|
||||
username="https://www.google.com/accounts/o8/id?id=AItOawkSq2FDpK2n66QRUxtqqdbyDuwgbQmUWus"
|
||||
nickname="Jimmy"
|
||||
subject="comment 2"
|
||||
date="2012-07-25T06:52:32Z"
|
||||
content="""
|
||||
Ah I was looking at the walkthrough on how to fix the issue, I had not thought about looking at the tips section. That tip fixed the issue for me, thanks.
|
||||
"""]]
|
||||
|
|
@ -0,0 +1,12 @@
|
|||
[[!comment format=mdwn
|
||||
username="https://me.yahoo.com/a/IAg3idYGk.joxsJb2WCxl20gig.0.8hS#d5165"
|
||||
nickname="Kelly"
|
||||
subject="comment 2"
|
||||
date="2012-05-10T15:01:15Z"
|
||||
content="""
|
||||
I think my comment a couple days ago got caught in the spam filter, so I'm reposting.
|
||||
What were the ideas to avoid parameterisation? What were the problems of parameterisation, other than just the current hardcoded assumptions?
|
||||
|
||||
Speaking of hash insecurity, http://static.usenix.org/events/hotos03/tech/full_papers/henson/henson_html/node8.html says compare-by-hash is a bad idea. As I understand, git doesn't have an option of verifying content matches when the hash matches when adding data to the object store (like zfs's \"dedup=verify\" option, which you can use even when using sha256), because the assumption is that the risk of collision (or at least just the risk of accidental collision) is negligible. Would it be worthwhile to add this option to git-annex?
|
||||
|
||||
"""]]
|
||||
|
|
@ -0,0 +1,11 @@
|
|||
[[!comment format=mdwn
|
||||
username="https://me.yahoo.com/a/IAg3idYGk.joxsJb2WCxl20gig.0.8hS#d5165"
|
||||
nickname="Kelly"
|
||||
subject="comment 2"
|
||||
date="2012-05-09T01:22:13Z"
|
||||
content="""
|
||||
What were the ideas to avoid parameterisation? What were the problems of parameterisation, other than just the current hardcoded assumptions?
|
||||
|
||||
Speaking of hash insecurity, http://static.usenix.org/events/hotos03/tech/full_papers/henson/henson_html/node8.html says compare-by-hash is a bad idea. As I understand, git doesn't have an option of verifying content matches when the hash matches when adding data to the object store (like zfs's \"dedup=verify\" option, which you can use even when using sha256), because the assumption is that the risk of collision (or at least just the risk of accidental collision) is negligible. Would it be worthwhile to add this option to git-annex?
|
||||
|
||||
"""]]
|
||||
|
|
@ -0,0 +1,18 @@
|
|||
[[!comment format=mdwn
|
||||
username="http://christian.amsuess.com/"
|
||||
nickname="chrysn"
|
||||
subject="comment 2"
|
||||
date="2012-05-11T17:40:20Z"
|
||||
content="""
|
||||
from my layman's standpoint, i think it would be feasible. i've suggested this previously, but not pushed it too much. quoting from [[my user page|users/chrysn]]:
|
||||
|
||||
* **would like git-annex to**: not be required any more as git itself learns to use cow filesystems to avoid abundant disk usage and gets better with sparser checkouts (git-annex might then still be a simpler tool that watches over what can be safely dropped for a sparser checkout)
|
||||
|
||||
*concerning hash sizes or parameterized hashes*: the problems with hash sizes could be avoided if instead of putting the objects in the \"normal\" object dir, barefiles would be managed in a similar way as packs are. when a new files gets added, they'd be cow-copied to ``.git/objects/bare/${HA}/${SH}``, and ``.git/objects/bareprefix/${HA}/${SH}`` would contain the \"blob ${SIZE}\0\" prefix that gets concatenated to the object body to form the object itself.
|
||||
|
||||
(maybe it'd even be sufficient to *just store the size* in the bareprefix, as all those objects would be blobs, but then again, some flexibility won't hurt.)
|
||||
|
||||
if the *pack file format* is flexible enough, the bareprefix files can get packed too. for the adventerous user who modifies bigfiles, the pack file mechanisms should be made aware of their presence, and be able to store deltas between them. the operations for applying those deltas would be difficult to optimize, and could be added at a later stage. a typical example could be storing a pdf file -- the pdf file format is designed for appending, so chances are the new version is just the old version plus several k at the end.
|
||||
|
||||
neither of that would affect git's *wire protocol*, so no compatibility problems. (it would be advisable to find a reasonable way to do sparse checkouts, though; something like \"server, pack and send your master, but make it sparse and don't include blobs >1mb\").
|
||||
"""]]
|
||||
|
|
@ -0,0 +1,10 @@
|
|||
[[!comment format=mdwn
|
||||
username="https://www.google.com/accounts/o8/id?id=AItOawlYu7QmD7wrbHWkoxuriaA9XcijM-g5vrQ"
|
||||
nickname="Royal"
|
||||
subject="Resolving conflict"
|
||||
date="2012-04-24T03:59:31Z"
|
||||
content="""
|
||||
Hi,
|
||||
Now I am able to resolve the conflict.
|
||||
Thank you.
|
||||
"""]]
|
||||
|
|
@ -0,0 +1,41 @@
|
|||
[[!comment format=mdwn
|
||||
username="https://www.google.com/accounts/o8/id?id=AItOawlYu7QmD7wrbHWkoxuriaA9XcijM-g5vrQ"
|
||||
nickname="Royal"
|
||||
subject="Resolving conflict"
|
||||
date="2012-04-23T15:49:30Z"
|
||||
content="""
|
||||
Thanks for the reply.
|
||||
|
||||
I am executing the following commands.
|
||||
|
||||
git init main
|
||||
cd main
|
||||
git annex init main
|
||||
echo a > a
|
||||
git annex add a
|
||||
git commit -m Initial
|
||||
git annex unlock a
|
||||
echo aa > a
|
||||
git annex add a
|
||||
git commit -m first
|
||||
git annex unlock a
|
||||
echo aaa > a
|
||||
git annex add a
|
||||
git commit -m second
|
||||
git log
|
||||
git cherry-pick <Hash of first commit>
|
||||
|
||||
--------------------
|
||||
Error:
|
||||
|
||||
error: could not apply 2be8f38... first
|
||||
hint: after resolving the conflicts, mark the corrected paths
|
||||
hint: with 'git add <paths>' or 'git rm <paths>'
|
||||
hint: and commit the result with 'git commit'
|
||||
|
||||
How can resolve the the above conflict.
|
||||
If I see the content of the file I will get the content of second commit.
|
||||
Is there any way I can get the content for first commit(Like in git we have 'theirs' option.)
|
||||
|
||||
Thank you.
|
||||
"""]]
|
||||
|
|
@ -0,0 +1,18 @@
|
|||
[[!comment format=mdwn
|
||||
username="https://www.google.com/accounts/o8/id?id=AItOawmBUR4O9mofxVbpb8JV9mEbVfIYv670uJo"
|
||||
nickname="Justin"
|
||||
subject="comment 2"
|
||||
date="2012-06-27T12:45:42Z"
|
||||
content="""
|
||||
I have a hacked up version of sharebox that does this.. I need to fix it up and push it to github..
|
||||
|
||||
the short of it is that you can do
|
||||
|
||||
def calculate_size(path):
|
||||
annexfile = os.path.basename(os.readlink(path))
|
||||
#SHA256-s2007550713--....
|
||||
size = annexfile.split(\"-\")[1]
|
||||
return int(size[1:])
|
||||
|
||||
to get the size of files.. a 'git-annex du' should be pretty straightforward...
|
||||
"""]]
|
||||
|
|
@ -0,0 +1,8 @@
|
|||
[[!comment format=mdwn
|
||||
username="https://www.google.com/accounts/o8/id?id=AItOawkSq2FDpK2n66QRUxtqqdbyDuwgbQmUWus"
|
||||
nickname="Jimmy"
|
||||
subject="comment 1"
|
||||
date="2012-06-23T08:00:12Z"
|
||||
content="""
|
||||
actually, scratch that, i found it. it was in _.git/annex/daemon.log_ along with the other bits and pieces
|
||||
"""]]
|
||||
|
|
@ -0,0 +1,8 @@
|
|||
[[!comment format=mdwn
|
||||
username="https://www.google.com/accounts/o8/id?id=AItOawkSq2FDpK2n66QRUxtqqdbyDuwgbQmUWus"
|
||||
nickname="Jimmy"
|
||||
subject="comment 2"
|
||||
date="2012-07-03T14:48:16Z"
|
||||
content="""
|
||||
Adding a date and timestamp would be a nice start to improving things.
|
||||
"""]]
|
||||
|
|
@ -0,0 +1,8 @@
|
|||
[[!comment format=mdwn
|
||||
username="https://www.google.com/accounts/o8/id?id=AItOawkSq2FDpK2n66QRUxtqqdbyDuwgbQmUWus"
|
||||
nickname="Jimmy"
|
||||
subject="comment 1"
|
||||
date="2012-07-02T16:25:55Z"
|
||||
content="""
|
||||
I've some binaries for OSX which can be found at <http://www.sgenomics.org/~jtang/gitbuilder-git-annex-x00-x86_64-apple-darwin10.8.0-binary/dist/> its just the master branch, and it's built on a system that runs macports. Binaries are built and updated whenever there are changes made to the master branch of git-annex.
|
||||
"""]]
|
||||
|
|
@ -0,0 +1,16 @@
|
|||
[[!comment format=mdwn
|
||||
username="https://www.google.com/accounts/o8/id?id=AItOawmLB39PC89rfGaA8SwrsnB6tbumezj-aC0"
|
||||
nickname="Tobias"
|
||||
subject="Thats a fair solution"
|
||||
date="2012-07-22T13:51:25Z"
|
||||
content="""
|
||||
Until you don't have(access to) an existing repository to clone from.
|
||||
|
||||
I really hope you revisit this when you come to the encryption part of the assistant.
|
||||
|
||||
Btw, I also run FreeBSD if you need a tester on that at some point.
|
||||
|
||||
Sincerely
|
||||
Tobias Ussing
|
||||
|
||||
"""]]
|
||||
|
|
@ -0,0 +1,8 @@
|
|||
[[!comment format=mdwn
|
||||
username="hannes"
|
||||
ip="130.226.142.243"
|
||||
subject="original repo git annex version"
|
||||
date="2012-07-08T11:55:42Z"
|
||||
content="""
|
||||
is 3.20120629
|
||||
"""]]
|
||||
Loading…
Add table
Add a link
Reference in a new issue