git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: A Large Angry SCM <gitzilla@gmail.com>
To: Junio C Hamano <junkio@cox.net>
Cc: Shawn Pearce <spearce@spearce.org>,
	git@vger.kernel.org, Petr Baudis <pasky@suse.cz>
Subject: Re: [PATCH] Added --mirror-all to git-fetch.
Date: Wed, 20 Sep 2006 11:42:30 -0700	[thread overview]
Message-ID: <45118B96.1080207@gmail.com> (raw)
In-Reply-To: <7vu032h1g1.fsf@assigned-by-dhcp.cox.net>

[-- Attachment #1: Type: text/plain, Size: 735 bytes --]

Junio C Hamano wrote:
[...]
> 
> Another possibility.  The mirror might want to do something
> like:
> 
>         .git/refs/remotes/davem/sparc-2.6.git/...
> 	.git/refs/remotes/torvalds/linux-2.6.git/...
> 	.git/refs/remotes/jgarzik/netdev-2.6.git/...
> 
> to be a super-mirror of related projects.  This would give a
> convenient way for the visitors to browse them all at one place,
> and would save object store.  There are minor details such as
> gitweb may not allow browsing refs/remotes and git-fetch may not
> let you fetch from refs/remotes (I haven't checked), but they
> are fixable as needed.
> 

This is what I do with the 2 attached, poorly named, scripts. Very 
convenient for watching some of my favorite projects. ;-)

[-- Attachment #2: fred.sh --]
[-- Type: application/x-shellscript, Size: 432 bytes --]

[-- Attachment #3: fred_history --]
[-- Type: text/plain, Size: 1188 bytes --]

export GIT_COMMITTER_NAME="@"
export GIT_AUTHOR_NAME="@"

./fred.sh git://www.kernel.org/pub/scm/git/git.git git/git

./fred.sh git://www.kernel.org/pub/scm/gitk/gitk.git gitk/gitk

./fred.sh git://www.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.11.y.git stable/linux-2.6.11.y
./fred.sh git://www.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.12.y.git stable/linux-2.6.12.y
./fred.sh git://www.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.13.y.git stable/linux-2.6.13.y
./fred.sh git://www.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.14.y.git stable/linux-2.6.14.y
./fred.sh git://www.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.15.y.git stable/linux-2.6.15.y
./fred.sh git://www.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.16.y.git stable/linux-2.6.16.y
./fred.sh git://www.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.17.y.git stable/linux-2.6.17.y

./fred.sh git://www.kernel.org/pub/scm/linux/kernel/git/tglx/history.git tglx/history

./fred.sh git://www.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git torvalds/linux-2.6
./fred.sh git://www.kernel.org/pub/scm/linux/kernel/git/torvalds/sparse.git torvalds/sparse

  reply	other threads:[~2006-09-20 18:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-19 23:28 [PATCH] Added --mirror-all to git-fetch Shawn Pearce
2006-09-19 23:41 ` Petr Baudis
2006-09-20 16:06 ` Junio C Hamano
2006-09-20 16:14   ` Petr Baudis
2006-09-20 16:21     ` Shawn Pearce
2006-09-20 16:34       ` Junio C Hamano
2006-09-20 16:49         ` Shawn Pearce
2006-09-20 17:13           ` Junio C Hamano
2006-09-20 17:31             ` Shawn Pearce
2006-09-20 17:50               ` Junio C Hamano
2006-09-20 18:42                 ` A Large Angry SCM [this message]
2006-09-20 21:36       ` Junio C Hamano
2006-09-20 21:42         ` Shawn Pearce
2006-09-20 18:29   ` 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=45118B96.1080207@gmail.com \
    --to=gitzilla@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=pasky@suse.cz \
    --cc=spearce@spearce.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;
as well as URLs for NNTP newsgroup(s).