I would use
find -name \*.avi -exec git annex add {} \;
but other than that, this seems fine. Depending on your level of OCD,
it might make sense to throw away the initial repo once your data is
clean and import everything in a clean one. That's what I do.
Richard
PS: There are various
On Wed, Dec 14, 2011 at 12:53 PM, Richard Hartmann
richih.mailingl...@gmail.com wrote:
I would use
find -name \*.avi -exec git annex add {} \;
That's substantially less performant, because it forks a whole new
tree of git / git-annex processes per file.
If we're getting picky, we should also
On Wed, Dec 14, 2011 at 14:15, Adam Spiers vcs-h...@adamspiers.org wrote:
That's substantially less performant, because it forks a whole new
tree of git / git-annex processes per file.
True.
Interesting - any particular reason for doing that?
Mainly that I will keep my repos for as long as
Hi,
Set up git-annex the other day using a centralised, non-annex-capable
git repository according to [1].
On my second machine, my laptop, I don’t seem to be able to push to the
centralised repository: I am getting the error one gets when one hasn’t
yet done a pull and done a merge, but I
Sean Whitton wrote:
On my second machine, my laptop, I don’t seem to be able to push to the
centralised repository: I am getting the error one gets when one hasn’t
yet done a pull and done a merge, but I definitely have:
| ! [rejected]git-annex - git-annex (non-fast-forward)
You
