A git flow for single-user development on multiple machines

[stahta01]

laserlight: Thank you the link.

I am now going to try a bare repo on my USB stick to solve this same problem.

Tim S.

[Mario F.]

Ok. stahta01 motivated me into giving this another go. Here's how I am doing it. Please advise if I am doing something wrong, or I can simplify the process.

At home computer (main development platform)
1. I clone the project repo into a bare copy on the usb stick: $ git clone --bare [mycomputer_projectdir] [usb_dir]
2. I add the usb to my remotes

At my office computer and at my laptop (secondary development platforms)
1. I clone the usb repo into a working tree repo
2. I do normal work; branch (or not), merge (or not) and commit.
3. I push work on the copy repo into the usb

Back at home(primary development platform)
1. I pull work done that day from the usb
2. I do normal work; branch (or not), merge (or not) and commit.
3. I push work on the copy repo into the usb

Next day at the office or laptop (secondary development platforms)
1. I pull from usb
2. I do normal work; branch (or not), merge (or not) and commit.
3. I push work on the copy repo into the usb

repeat...

[Yarin]

If it were my personal problem, I'd definitely leave the repo on the stick.

Seconded. I don't know why Mario fears corruption. If you can't trust the drive for the centeral repo, I don't see how you could trust it any more for transferring updates among repos.

[Mario F.]

Seconded. I don't know why Mario fears corruption. If you can't trust the drive for the centeral repo, I don't see how you could trust it any more for transferring updates among repos.

Yeah. I ditched that thought soon after. I've had some problems in the past with usb sticks becoming corrupted out of nowhere and have been badly harmed in one particular incident. So I confess I'm a little paranoid when it comes to those things. But with a distributed system like git, it really there's nothing to fear about a corrupt usb stick.

[stahta01]

No idea what is the right way this is what I am trying; I am a Git newbie of a several months (might be a year but, it not 2 years.)

I run the commands in the Git folder on the hard drive.
P: Is the flash drive letter.

git init --bare P:/CI_Git_Projects/DCRABBIT_9.62.git

git remote add flashdrive P:/CI_Git_Projects/DCRABBIT_9.62.git

git config --local push.default simple

git push flashdrive

It seems to work for me; but, I am not really using it to hold important data. I use Github like site for that.

I am just storing the compiler binaries used to build in this flashdrive repo.

Tim S.

[phantomotap]

There are already four copies of the repo, how many more should we add? Another 15?

O_o

Did Mario F. say "I intend to visit each machine every update to synchronization the repository."?

Nope. You are trying to say "three computers plus one stick".

The reality is that only the current machine being used for active development has a current copy of the repository. When the live repository is synchronized with the stick, you have a single backup of the current data. You have one point of recovery should either the stick of the development machine fail. If two devices fail, you can't recover the data so you do not have two backups.

*shrug*

I don't consider an outdated branch to be a legitimate backup, but I guess you could pretend that you have four backups.

Soma

[laserlight]

Ok. stahta01 motivated me into giving this another go. Here's how I am doing it. Please advise if I am doing something wrong, or I can simplify the process.

Looks fine by me. Since you're apparently the only developer, you don't have to worry about merge or rebase unless you say, fail to complete a unit of work such that you leave it uncommitted, then go elsewhere and do another unit of work that you push to the USB stick repo.