The confusion there would be public vs private branches (never publish 

> to a public branch that _will_ be used by team mates). But I would still 
> expect that individual developers would need to fixup and rework their 
> private branches before publishing to a public branch. And if they have 
> two machines they need to be able to synchronise their private branch 
> between the machines, which is my use case as I get to grips with 
> Linux/Ubuntu. 

How about creating a computer-specific branch, instead of both computers 
working on "master", you work from home on a branch "wip-home" and at work 
you use the branch "wip-work". Then, occasionally, or before you want to 
merge your work to master, you create a "wip-prepare" where you 
cherry-pick, merge and rebase whatever you want from the wip branches.

Regarding the intuitiveness/documentation of git rebase.. I think that's 
basically what separates Git from Mercurial, with their immutable and 
static public branches. At this stage, I don't know if there's anything we 
can do but say "you just need to fully grok rebase and reset when using Git 
extensively". It bothers me, but at the moment I can't think of an option 
for this.

You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
For more options, visit

Reply via email to