| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
| |
that link to the same content.
|
| | |
|
| |
|
|
| |
made to it.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Generalized LocationLog to PresenceLog, and use a presence log to record
urls for the web special remote.
|
| |
|
|
| |
It was always imported qualified as Git anyway
|
| | |
|
| |
|
|
|
| |
GitRepo is getting too large an interface; these all fit nicely into a
submodule.
|
| |\
| |
| |
| |
| | |
Conflicts:
debian/changelog
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
Now that branches are more likely, unused needs to more explicitly warn
that it does not look in them.
|
| | |
| |
| |
| | |
but write the index file a lot, so slow
|
| | |
| |
| |
| |
| |
| | |
That sucking sound is a whole page of code vanishing to be replaced with
return . catMaybes . map (logFileKey . takeFileName) =<< Branch.files
What can I say, git is my database, and haskell my copilot.
|
| | | |
|
| | |
| |
| |
| |
| | |
Many more commands can work in bare repos now, thanks to the git-annex
branch.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Do not set annex.version whenever any command is run. Just do it in init.
This ensures that, if a repo has annex.version=3, it has a git-annex
branch, so we don't have to run a command every time to check for the
branch.
Remove the old ad-hoc logic for v0 and v1, to simplify version checking.
|
| | |
| |
| |
| | |
.. and I think that's everything that will use the branch
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
stop changing gitattributes on init
create git-annex branch on init
ugly special case for init in a bare repository goes away, yay!
git annex init is also faster, at least in a large existing repo, as
it does not need to run the slow 'git add'
|
| | |
| |
| |
| | |
v2 upgrade will undo them
|
| |/
|
|
| |
It will need to run in Annex so it can use Branch
|
| | |
|
| |
|
|
|
|
|
|
| |
get not honoring --from has surprised me a few times, so least surprise
suggests it should just behave like copy --from. This leaves the difference
between get and copy being that copy always requires the remote to copy
from, while get will decide whether to get a file from a key/value store or
a remote.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Avoid git reset here too, so I no longer need to care that it's much more
expensive than seems wise (but I asked the git list about that anyway).
It's not necessary to reset the staged file content from the index, as
the `git add` of the the symlink will replace it anyway.
`git commit` of unlocked files is still slow, since git still has to shove
their entire content into the index, only to have it be thrown away. So it's
still better to use `git annex add`
|
| |
|
|
|
| |
Previously, lock would skip files that had staged changes, but that is
counterintuitive, I think.
|
| |
|
|
| |
reset`, and only running `git checkout` once, even when many files are being locked.
|
| | |
|
| |
|
|
| |
Introduced in 43f0a666f0f6cc152a2b778921831d6d7daedcaf
|
| | |
|
| |
|
|
|
| |
Display the name of the remote being checked, with "." for the current
remote, echoing the way describe takes that to change its description.
|
| |
|
|
| |
list available remotes in case user wanted to use or change one of them
|
| | |
|
| |
|
|
|
| |
Otherwise, the user sees only a rsync protocol error message and then
git-annex's less specific failure message.
|
| |
|
|
|
| |
Just more golfing.. I am pretty sure something in a library somewhere can
do this, but I have been unable to find it.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
Joey Hess