correct spelling mistakes
This commit is contained in:
Edward Betts
Joey Hess
parent
5e6ced7d0f
commit
0750913136
52 changed files with 69 additions and 69 deletions
|
|
@ -11,7 +11,7 @@ That fixed one last Windows bug that was disabled in the test suite:
|
|||
`git annex add ..\subdir\file` will now work.
|
||||
|
||||
I am re-installing the Android autobuilder for 2 reasons: I noticed I had
|
||||
accidentially lost a patch to make a library use the Android SSL cert directory,
|
||||
accidentally lost a patch to make a library use the Android SSL cert directory,
|
||||
and also a new version of GHC is very near to release and so it makes sense
|
||||
to update.
|
||||
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ Today I put together a lot of things I've been thinking about:
|
|||
git-annex user to upgrade their repository, and would be very painful.
|
||||
It's hard to imagine a change that is worth that amount of pain.
|
||||
* There are other changes some would like to see (like lower-case object
|
||||
hash directory names) that are certianly not enough to warrant a flag
|
||||
hash directory names) that are certainly not enough to warrant a flag
|
||||
day repo format upgrade.
|
||||
* It would be nice to let people who want to have some flexibility to play
|
||||
around with changes, in their own repos, as long as they don't a)
|
||||
|
|
@ -32,7 +32,7 @@ The main limitations are:
|
|||
|
||||
I built all the infrastructure for this today. Basically, the git-annex
|
||||
branch gets a record of all tunings that have been applied, and they're
|
||||
automatically propigated to new clones of a repository.
|
||||
automatically propagated to new clones of a repository.
|
||||
|
||||
And I implemented the first tunable setting:
|
||||
|
||||
|
|
@ -40,10 +40,10 @@ And I implemented the first tunable setting:
|
|||
|
||||
This is definitely an experimental feature for now.
|
||||
`git-annex merge` and similar commands will detect attempts to merge
|
||||
between incompatably tuned repositories, and error out. But, there are a
|
||||
between incompatibly tuned repositories, and error out. But, there are a
|
||||
lot of ways to shoot yourself in the foot if you use this feature:
|
||||
|
||||
* Nothing stops `git merge` from merging two incompatable repositories.
|
||||
* Nothing stops `git merge` from merging two incompatible repositories.
|
||||
* Nothing stops any version of git-annex older from today from merging
|
||||
either.
|
||||
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@ Reduced activity this week (didn't work on the assistant after all),
|
|||
but several things got done:
|
||||
|
||||
Monday: Fixed `fsck --fast --from remote` to not fail when the remote
|
||||
didn't support fast copy mode. And dealt with an incompatability in S3 bucket
|
||||
didn't support fast copy mode. And dealt with an incompatibility in S3 bucket
|
||||
names; the old hS3 library supported upper-case bucket names but the new
|
||||
one needs them all in lower case.
|
||||
|
||||
|
|
|
|||
|
|
@ -14,8 +14,8 @@ and so lets a lot of queries be done much faster. The implementation
|
|||
should make it easy to add --batch to more plumbing commands as needed,
|
||||
and could probably extend to non-plumbing commands too.
|
||||
|
||||
Today: The first 5 hours involved an incompatable mess of ssh and rsync
|
||||
versions on Windows. A gordian knot of brokenness and depedency hell.
|
||||
Today: The first 5 hours involved an incompatible mess of ssh and rsync
|
||||
versions on Windows. A Gordian knot of brokenness and dependency hell.
|
||||
I finally found a solution which involves downgrading the cygwin rsync
|
||||
to an older version, and using msysgit's ssh rather than cygwin's.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
Made a release this morning, mostly because the release earlier this week
|
||||
turns out to have accidentially removed several options from `git annex copy`.
|
||||
turns out to have accidentally removed several options from `git annex copy`.
|
||||
|
||||
Spent some time this afternoon improving how git-annex shuts down when
|
||||
--time-limit is used. This used to be a quick and dirty shutdown, similar
|
||||
|
|
|
|||
|
|
@ -3,13 +3,13 @@ one more feature to it today: Full anacron style scheduling. So a fsck can
|
|||
be scheduled to run once per week, or month, or year, and it'll run the
|
||||
fsck the next time it's available after that much time has passed. The nice
|
||||
thing about this is I didn't have to change Cronner *at all* to add this,
|
||||
just improved the Recurrance data type and the code that calculates when
|
||||
just improved the Recurrence data type and the code that calculates when
|
||||
to run events.
|
||||
|
||||
Rest of the day I've been catching up on some bug reports. The main bug I
|
||||
fixed caused git-annex on Android to hang when adding files. This turns out
|
||||
to be because it's using a new (unreleased) version of git, and
|
||||
`git check-attr -z` output format has changed in an incompatable way.
|
||||
`git check-attr -z` output format has changed in an incompatible way.
|
||||
|
||||
I am currently 70 messages behind, which includes some ugly looking bug
|
||||
reports, so I will probably continue with this over the next couple days.
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
git-annex 6.20160419 has a rare security fix.
|
||||
A [bug](http://git-annex.branchable.com/bugs/External_special_remote_broken__63__/) made encrypted special
|
||||
remotes that are configured to use chunks accidentially expose the checksums
|
||||
remotes that are configured to use chunks accidentally expose the checksums
|
||||
of content that is uploaded to the remote. Such information is supposed to
|
||||
be hidden from the remote's view by the encryption. The same bug also made
|
||||
resuming interrupted uploads to such remotes start over from the beginning.
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
subject="comment 1"
|
||||
date="2016-04-29T10:26:22Z"
|
||||
content="""
|
||||
> A bug made encrypted special remotes that are configured to use chunks accidentially expose the checksums of content that is uploaded to the remote. Such information is supposed to be hidden from the remote's view by the encryption.
|
||||
> A bug made encrypted special remotes that are configured to use chunks accidentally expose the checksums of content that is uploaded to the remote. Such information is supposed to be hidden from the remote's view by the encryption.
|
||||
|
||||
What should the users do to repair this situation? How can the exposed checksums be removed from the remote? Is a `git annex sync` enough?
|
||||
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
A productive day of small fixes. Including a change to deal with an
|
||||
incompatability in git 2.9's commit.gpgsign, and couple of fixes
|
||||
incompatibility in git 2.9's commit.gpgsign, and couple of fixes
|
||||
involving gcrypt repositories.
|
||||
|
||||
Also several improvements to cloning from repositories where an adjusted
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue