updates for bare repo support

This commit is contained in:
Joey Hess 2011-03-03 15:59:16 -04:00
parent 486f882471
commit a9d0538da5
6 changed files with 23 additions and 6 deletions

2
debian/changelog vendored
View file

@ -10,6 +10,8 @@ git-annex (0.22) UNRELEASED; urgency=low
option. option.
* New backends: SHA512 SHA384 SHA256 SHA224 * New backends: SHA512 SHA384 SHA256 SHA224
* fsck: Check for and repair location log damage. * fsck: Check for and repair location log damage.
* Git annexes can now be attached to bare git repositories. Due to popular
demand.
-- Joey Hess <joeyh@debian.org> Sun, 13 Feb 2011 00:48:02 -0400 -- Joey Hess <joeyh@debian.org> Sun, 13 Feb 2011 00:48:02 -0400

View file

@ -1,5 +1,12 @@
Due to popular demand, git-annex can now be used with bare repositories. Due to popular demand, git-annex can now be used with bare repositories.
So, for example, you can stash a file away in your
repos's origin: `git annex move mybigfile --to origin`
Of course, for that to work, the bare repository has to be on a system with
[[git-annex-shell]] installed. If "origin" is on gitweb, you still can't
use git-annex to there.
**This is still an experimental feature!** **This is still an experimental feature!**
Known to work ok: Known to work ok:

View file

@ -24,3 +24,6 @@ A possible other approach to the state recording repo is to not
record state changes on the remote in that case. Git-annex already record state changes on the remote in that case. Git-annex already
records remote state changes locally whenever it modifies the state of a records remote state changes locally whenever it modifies the state of a
remote. --[[Joey]] remote. --[[Joey]]
> And... [[done]]! See [[/bare_repositories]] for current status
> and gotchas. --[[Joey]]

View file

@ -3,8 +3,8 @@ git-annex from being used on USB keys, that would typically
be VFAT formatted: be VFAT formatted:
- Use of symlinks, which VFAT does not support. Very hard to fix. - Use of symlinks, which VFAT does not support. Very hard to fix.
One possibility is to add [[bare_git_repos]] support, then Instead, just use [[/bare_repositories]] on the key,
a git repo on a thumb drive could be used to transfer data. they're supported now.
- Use of ":" in filenames of object files, also not supported. - Use of ":" in filenames of object files, also not supported.
Could easily be fixed by reorganizing the object directory. Could easily be fixed by reorganizing the object directory.

View file

@ -7,3 +7,8 @@ new cannot see origin.
the .git/config has "url=/.../orig/.git". Apparently git is ok with that the .git/config has "url=/.../orig/.git". Apparently git is ok with that
weird construction; probably it treats it as a bare git repo. But git-annex weird construction; probably it treats it as a bare git repo. But git-annex
just sees a directory w/o a .git subdir, and gives up. just sees a directory w/o a .git subdir, and gives up.
---
Just tested, and the new support for bare repositories didn't solve this.
--[[Joey]]

View file

@ -327,10 +327,10 @@ Here are all the supported configuration settings.
from using this remote by default. (You can still request it be used from using this remote by default. (You can still request it be used
by the --from and --to options.) by the --from and --to options.)
This is, for example, useful if the remote is a bare repository, This is, for example, useful if the remote is located somewhere
which git-annex does not currently support. Or, it could be used without [[git-annex-shell]]. (For example, if it's on GitHub).
if the network connection between two repositories is too slow Or, it could be used if the network connection between two
to be used normally. repositories is too slow to be used normally.
* `remote.<name>.annex-uuid` * `remote.<name>.annex-uuid`