git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Carl Baldwin <cnb@fc.hp.com>
Cc: git@vger.kernel.org
Subject: Re: How is working on arbitrary remote heads supposed to work in Cogito (+ PATCH)?
Date: Sat, 13 Aug 2005 00:48:32 -0700	[thread overview]
Message-ID: <7vacjmqnu7.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20050813041114.GA29412@hpsvcnb.fc.hp.com> (Carl Baldwin's message of "Fri, 12 Aug 2005 22:11:14 -0600")

Carl Baldwin <cnb@fc.hp.com> writes:

> On Fri, Jul 29, 2005 at 08:10:51AM +0000, Petr Baudis wrote:
>> 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.
>
> Sorry to join the game so late.  I've only read this thread now.

Just in case you have not noticed, the push in 0.99.4 and
onwards does exactly that.  Please see git-push-script.txt in
the Documentation/ directory --- oops, there is no such thing.

Please see git-send-pack.txt instead, and if you feel like it, I
would appreciate a patch to add the missing documentation for
git-push-script ;-).

What's not supported well yet is the opposite --- downloading
multiple refs and dealing with them.

Johannes Schindelin calls this "reverse push", and I think that
is really a good name to describe what it does.  It takes a
remote repository and possibly multiple refs, downloads the
objects to complete the named remote references, and updates the
local refs only if the remote refs are fast forward children of
the local refs being replaced, just like "push" fast forwards
the remote refs using the local refs.  In other words, given
<src> and <dst> repository, the following should do the same
thing:

    On <src> repository machine, with GIT_DIR being the <src> repository:
    $ git push <dst> <ref-local-name>:<ref-remote-name>...

    On <dst> repository machine, with GIT_DIR being the <dst> repository:
    $ git pull <src> <ref-remote-name>:<ref-local-name>...

Johannes posted a script on the list a couple of days ago, which
should work well, except that it was written before the
git-fetch-pack command was updated to natively download from
multiple refs, so it does not know how to fetch multiple refs at
a one go.

-jc

  reply	other threads:[~2005-08-13  7:48 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 [this message]
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=7vacjmqnu7.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=cnb@fc.hp.com \
    --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.
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).