git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: git@vger.kernel.org
Subject: Updated multi-head downloads and $GIT_DIR/remotes/ support
Date: Sat, 20 Aug 2005 11:13:10 -0700	[thread overview]
Message-ID: <7vvf20o4sp.fsf@assigned-by-dhcp.cox.net> (raw)

Now I think all the pieces are glued together.  I'll send the
following patches, which are already in the proposed updates
branch.

I sent an early WIP for some of them, but the patches are
reorganized for easier review and applies on top of the current
"master" branch.

This series consists of the following:

    Start adding the $GIT_DIR/remotes/ support.
    Multi-head fetch.
    Retire git-parse-remote.
    Infamous 'octopus merge'
    Make "git pull" and "git fetch" default to origin
    Use .git/remote/origin, not .git/branches/origin.

The issues I discussed in "Multi-head fetches, pulls, and a King
Ghidorah" are addressed there, and the examples in "MyGITDay"
message I sent earlier should work with these patches.  I'll
work on adding some documentation, maybe in howto or tutorial
format, over the weekend.

-jc

             reply	other threads:[~2005-08-20 18:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-20 18:13 Junio C Hamano [this message]
2005-08-20 18:22 ` [PATCH] Start adding the $GIT_DIR/remotes/ support Junio C Hamano
2005-08-20 18:25 ` [PATCH] Multi-head fetch Junio C Hamano
2005-08-20 18:25 ` [PATCH] Retire git-parse-remote Junio C Hamano
2005-08-20 18:25 ` [PATCH] Infamous 'octopus merge' Junio C Hamano
2005-08-20 18:25 ` [PATCH] Make "git pull" and "git fetch" default to origin Junio C Hamano
2005-08-20 18:25 ` [PATCH] Use .git/remote/origin, not .git/branches/origin Junio C Hamano

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=7vvf20o4sp.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --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).