Git development
 help / color / mirror / Atom feed
From: Josef Weidendorfer <Josef.Weidendorfer@gmx.de>
To: git@vger.kernel.org
Subject: Re: How is working on arbitrary remote heads supposed to work in Cogito (+ PATCH)?
Date: Fri, 29 Jul 2005 11:10:08 +0200	[thread overview]
Message-ID: <200507291110.08417.Josef.Weidendorfer@gmx.de> (raw)
In-Reply-To: <7vmzo6jbme.fsf@assigned-by-dhcp.cox.net>

Hi,

On Friday 29 July 2005 09:48, you wrote:
> Petr Baudis <pasky@suse.cz> writes:
> > So, what do you mean by "clone" here? And what command should I use for
> > pushing then?
...
> 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.

OK, that is your opinion and your work flow. But porcelains perhaps would like 
to allow other work flows, even if it seems confusing for you.

And I think the problem here simple is that send-pack *forces* local and 
remote head names to be the same. This is forcing policy to porcelains, but 
GIT should be only about plumbing.

Perhaps the solution is to allow more flexibility in GIT.
What about introducing an additional environment GIT_REFS_DIR?
When using send-pack, the porcelain would set this variable to a directory 
containing a 1:1 name relationship to the remote repository.

Josef

  parent reply	other threads:[~2005-07-29  9:11 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
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 [this message]
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=200507291110.08417.Josef.Weidendorfer@gmx.de \
    --to=josef.weidendorfer@gmx.de \
    --cc=git@vger.kernel.org \
    /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