Re: How is working on arbitrary remote heads supposed to work in Cogito (+ PATCH)?

Dear diary, on Fri, Jul 29, 2005 at 09:48:57AM CEST, I got a letter
where Junio C Hamano [off-list ref] told me that...

Petr Baudis [off-list ref] writes:

quoted

Aha, so it seems our problem is hopefully only in terminology, great.

So, what do you mean by "clone" here? And what command should I use for
pushing then?

Notice I never used the word "clone" in what I said.

quoted

However, I happen to think that two repositories
you use send-pack (not _CLONE_ which uses completely different
protocol)

(emphasis mine ;-)

Now, A may happen to be on my home machine and B may happen be
on my notebook, meaning the owner of A and B are both myself.
But even in that case I would still work by "pulling from A"
when I am on B, and "pulling from B" when I am on A.  In other
words, "pulling" is the only patch flow mechanism I would use.

I use cg-push on my notebook, given that the notebook might not happen
to have public IP address in some cases, or might be behind some
corporate firewall, or that I'm lazy to ssh to my home machine in order
to pull.

Pushing is only for publication and I treat it as just a
GIT-aware rsync/mirror, nothing more.  I have a feeling that
your workflow is different and you plan to use both push and
pull for normal patch flows.  This distinction is probably where
the disagreement comes from.

Exactly. I want much more freedom in pushing, the only requirement being
that "the to-be-replaced remote head is ancestor of the to-be-pushed
local head". I think (am I wrong?) git-send-pack localhead:remotehead
would work just fine for me, the only thing I need is the support for
different local and remote head names.

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
If you want the holes in your knowledge showing up try teaching
someone.  -- Alan Cox