| Commit message (Collapse) | Author | Age |
|---|
| ... | |
| |
|
|
|
| |
There are two types of commands; those that access the repository and those
that don't. Sorted.
|
| | |
|
| |
|
|
| |
etc. Use git-annex upgrade when you're ready to run this version.
|
| |
|
|
| |
information.
|
| | |
|
| | |
|
| |
|
|
| |
doesn't test remote functionality.. but that may be working too now
|
| | |
|
| |
|
|
| |
key is now specified as the full key, no --backend needed
|
| | |
|
| |
|
|
|
|
|
| |
It compiles. It sorta works. Several subcommands are FIXME marked and
broken, because things that used to accept separate --backend and --key
params need to be changed to accept just a --key that encodes all the key
info, now that there is metadata in keys.
|
| | |
|
| |
|
|
|
|
|
| |
When adding files to the annex, the symlinks pointing at the annexed
content are made to have the same mtime as the original file. While git
does not preserve that information, this allows a tool like metastore to be
used with annexed files.
|
| |
|
|
| |
or may not match locale settings, any attempt to decode filenames will fail for some files. So instead, do all output in binary mode.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Most will just abort. init does a basic init and gives a command to
run elsewhere to finish it.
|
| |
|
|
|
| |
Since they need to stage changes, they would actually, if allowed to run,
succeed, but wipe out existing trust.log content.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
This assumes that changes to content in bare repos are made from some
non-bare repo, and that the location log is updated on that side.
That's true for move --from and move --to.
It's *not* true for dropkey and setkey and recvkey. But those are plumbing
level commands, so I guess it's ok to assume that someone running those
in a bare repo knows what they're doing. And git-annex-shell is used to
run those, and if the bare repo is non-local, it needs to be able to use
them even though they cannot update the location log. So this seems
unavoidable.
|
| | |
|
| | |
|
| |
|
|
|
| |
So, I have a type checked safe handling of filenames starting with dashes,
throughout the code.
|
| |
|
|
| |
utility it will be escaped to avoid it being interpreted as an option.
|
| |
|
|
|
|
|
|
| |
Based on http://hackage.haskell.org/trac/ghc/ticket/3307 ,
whether FilePath contains decoded unicode varies by OS.
So, add a configure check for it.
Also, renamed showFile to filePathToString
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Internally, the filenames are stored as un-decoded unicode.
I tried decoding them, but then haskell tries to access the wrong files.
Hmm.
So, I've unhappily chosen option "B", which is to decode filenames before
they are displayed.
|
| |
|
|
| |
one file at a time.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Need to find the absolute repo path before looking up the full info for the
repo. Otherwise, it doesn't find the right full info.
|
| |
|
|
| |
it was dropping the config map for the repos it changed
|
| | |
|
| | |
|
| |
|
|
| |
Local repos with the same path are not different. :)
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
added uuid.log repos
group repos by host
avoid displaying most urls
display remote names on edges
still some bugs
|
| |
|
|
|
|
|
|
|
|
|
| |
Still todo:
- add repos from uuid.log that were not directly found
- group repos into their respective hosts
- display inaccessible repos and broken remote connections in red
- anonymize the url display somewhat, so the maps can be shared
- use uuid info to tell when two apparently different repos are actually
the same repo accessed in different ways
|
| | |
|
| |
|
|
|
| |
to avoid some confusing behavior with the pre-commit hook, which would see
some types of commits after an unannex as checking in of an unlocked file.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
more efficient and idiomatic
I did try using Set.difference, it's still slower than my method.
|
Joey Hess
Michael Kenney