Magic mirroring
2006-10-10 12:01 am I'm in the process of uploading my most recent take of "Someplace in the
Net", along with enough version control information to make it possible
for a collaborator (waves at
cflute) to upload some additions.
I'm almost certainly doing it wrong; possibly somebody more familiar with
the git version-control system could tell me how to do what I
really want to do.
I really only need to upload the last, good take and the git
objects that correspond to it. What I did was clone the repository in my
track directory and delete all the Audacity projects but the one I wanted
to upload. That's fine, but it doesn't delete them all from the
git repository. Normally you don't want it to, but in this
case I really wanted to upload only the current state. That's 200MB of
history I don't want to push up through my skinny little ADSL pipe.
For the moment, I punted: I deleted the cloned repository, and made
myself a new one without the baggage. I suspect there's a way to do what
I want using branches -- any git experts out there on my
flist?
It's going to be even more fun going the other way, since there's no good
way to give other people upload access to my ISP's shell account.
Eventually it's going to have to go onto a server I have total control
over, which realistically means the one hanging off my DSL line. For now,
git has ways of packaging up a set of changes into a file;
that'll work, but I'll have to document it.
Anything to avoid doing actual work...
no subject
Date: 2006-10-10 07:34 am (UTC)no subject
Date: 2006-10-10 01:55 pm (UTC)git, some having to do with work. There's also the fact that it's a distributed VCS, so it's designed to deal with multiple repositories -- every working directory includes its own. That in turn is really nice in a situation where it takes a couple of hours to upload a tree.no subject
Date: 2006-10-10 07:40 am (UTC)