From: Petr Baudis <pasky@suse.cz>
To: Junio C Hamano <junkio@cox.net>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Josef Weidendorfer <Josef.Weidendorfer@gmx.de>,
git@vger.kernel.org
Subject: Re: How is working on arbitrary remote heads supposed to work in Cogito (+ PATCH)?
Date: Fri, 29 Jul 2005 09:06:29 +0200 [thread overview]
Message-ID: <20050729070628.GA24895@pasky.ji.cz> (raw)
In-Reply-To: <7v4qaeqrh3.fsf@assigned-by-dhcp.cox.net>
Dear diary, on Fri, Jul 29, 2005 at 04:24:40AM CEST, I got a letter
where Junio C Hamano <junkio@cox.net> told me that...
> Petr Baudis <pasky@suse.cz> writes:
>
> > One of the Cogito design bits is that branch name is something local to
> > the repository. When you are adding a branch, the local name you assign
> > it is your private thing repository-wise, and doesn't have to have any
> > correlation to other repositories you might interact width.
>
> I do not disagree with that. I think branch name is mostly a
> local matter. However, I happen to think that two repositories
> you use send-pack (not clone which uses completely different
> protocol) to sync one from the other are semantically equivalent
> ones, except that the destination may be a strict subset. I
> think of it as "a copy I throw at a public place to show what I
> have in my private repository I work in", so,...
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?
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
If you want the holes in your knowledge showing up try teaching
someone. -- Alan Cox
next prev parent reply other threads:[~2005-07-29 7:07 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 [this message]
2005-07-29 7:48 ` Junio C Hamano
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050729070628.GA24895@pasky.ji.cz \
--to=pasky@suse.cz \
--cc=Johannes.Schindelin@gmx.de \
--cc=Josef.Weidendorfer@gmx.de \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).