From: Junio C Hamano <junkio@cox.net>
To: Petr Baudis <pasky@suse.cz>
Cc: git@vger.kernel.org
Subject: Re: How is working on arbitrary remote heads supposed to work in Cogito (+ PATCH)?
Date: Fri, 29 Jul 2005 00:48:57 -0700 [thread overview]
Message-ID: <7vmzo6jbme.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20050729070628.GA24895@pasky.ji.cz> (Petr Baudis's message of "Fri, 29 Jul 2005 09:06:29 +0200")
Petr Baudis <pasky@suse.cz> writes:
> 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.
What I mean by "a semantically equivalent two repositories,
potentially one being a strict subset of the other" is you can
pull head A from one or head A from the other and can get the
same result (although one may and the other may not have head
B). And naturally you use send-pack for pushing.
If I "clone" from repository A to create a repository B, I would
never "push back" from B to A. Instead I would ask a person who
owns A to "pull from B". My impression is the patch flow in the
kernel circle works like that (although I have never been in
that circle).
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.
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.
And I strongly suspect that the primary reason that I "simply do
not get it" after reading your messages is because my mental
model is strongly molded into what Linus taught us. I have to
unlearn things...
next prev parent reply other threads:[~2005-07-29 7:54 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-27 12:58 How is working on arbitrary remote heads supposed to work in Cogito (+ PATCH)? Josef Weidendorfer
2005-07-28 1:32 ` Junio C Hamano
2005-07-28 12:08 ` Petr Baudis
2005-07-28 13:07 ` Johannes Schindelin
2005-07-28 15:35 ` Petr Baudis
2005-07-28 15:56 ` Johannes Schindelin
2005-07-28 16:18 ` Petr Baudis
2005-07-28 16:52 ` Junio C Hamano
2005-07-28 17:32 ` Johannes Schindelin
2005-07-28 18:45 ` Ryan Anderson
2005-07-28 18:51 ` Johannes Schindelin
2005-07-28 18:39 ` Petr Baudis
2005-07-28 18:49 ` Johannes Schindelin
2005-07-28 19:47 ` Matthias Urlichs
2005-07-28 20:14 ` Johannes Schindelin
2005-07-29 7:11 ` Petr Baudis
2005-07-29 2:24 ` Junio C Hamano
2005-07-29 7:06 ` Petr Baudis
2005-07-29 7:48 ` Junio C Hamano [this message]
2005-07-29 8:10 ` Petr Baudis
2005-07-29 8:54 ` Junio C Hamano
2005-07-29 9:40 ` Petr Baudis
2005-07-29 10:57 ` Johannes Schindelin
2005-07-29 11:13 ` Petr Baudis
2005-07-29 12:26 ` Johannes Schindelin
2005-07-29 12:28 ` Petr Baudis
2005-07-30 2:11 ` Junio C Hamano
2005-07-29 20:40 ` Matthias Urlichs
2005-07-30 22:16 ` Junio C Hamano
2005-08-13 4:11 ` Carl Baldwin
2005-08-13 7:48 ` Junio C Hamano
2005-08-15 16:23 ` Carl Baldwin
2005-08-15 23:55 ` Johannes Schindelin
2005-07-29 9:10 ` Josef Weidendorfer
2005-07-28 21:13 ` Matthias Urlichs
2005-07-29 7:14 ` Petr Baudis
2005-07-28 18:53 ` Josef Weidendorfer
2005-07-28 19:19 ` Unnamed branches Petr Baudis
2005-07-28 16:14 ` How is working on arbitrary remote heads supposed to work in Cogito (+ PATCH)? Junio C Hamano
2005-07-28 16:23 ` Petr Baudis
2005-07-28 15:35 ` Petr Baudis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vmzo6jbme.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=pasky@suse.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox