From: Junio C Hamano <junkio@cox.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: Multi-head fetches, pulls, and a King Ghidorah
Date: Fri, 19 Aug 2005 03:25:13 -0700 [thread overview]
Message-ID: <7vslx6z0ja.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.63.0508191039460.11916@wgmdd8.biozentrum.uni-wuerzburg.de> (Johannes Schindelin's message of "Fri, 19 Aug 2005 11:14:54 +0200 (CEST)")
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> Hi,
>
> If I understand correctly, the multi-head fetch would not write any ref if
> used like this:
>
> git fetch remote:repository/ head tail
>
> but it would try a fast-forward when used like this:
>
> git fetch remote:repository/ head:head tail:tail
>
> Correct? If yes: This is fantastic! It obsoletes my dumb script.
That is the intent, but what is currently in "pu" is somewhat
broken.
next prev parent reply other threads:[~2005-08-19 10:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-19 7:45 Multi-head fetches, pulls, and a King Ghidorah Junio C Hamano
2005-08-19 9:14 ` Johannes Schindelin
2005-08-19 10:25 ` Junio C Hamano [this message]
2005-08-20 3:07 ` My GIT Day Junio C Hamano
2005-08-20 11:02 ` Johannes Schindelin
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=7vslx6z0ja.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=Johannes.Schindelin@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