All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Junio C Hamano <junkio@cox.net>
Cc: Ryan Anderson <ryan@michonline.com>,
	git@vger.kernel.org, Linus Torvalds <torvalds@osdl.org>
Subject: Re: [PATCH] Add git-relink-script to fix up missing hardlinks
Date: Sun, 26 Jun 2005 15:44:15 -0400	[thread overview]
Message-ID: <42BF058F.8010301@pobox.com> (raw)
In-Reply-To: <7vy88wq5hs.fsf@assigned-by-dhcp.cox.net>

Junio C Hamano wrote:
> I am a bit puzzled, though, why Jeff was the original requestor
> for this feature --- I thought he handles 50 heads in one
> repository which means there is no multiple repositories to
> relink across.

Sure there are.  Just watching my submissions on the mailing list, you 
can see ones mentioned such as "misc-2.6", "libata-dev", "netdev-2.6", etc.:

[jgarzik@pretzel repo]$ ls -FC
  config-2.4      ethtool/    libata-dev/  netdev-2.6/     sparse/
  config-2.6      git/        linux-2.6/   old-SCM/
  config-2.6-uml  git-tools/  misc-2.6/    scsi-misc-2.6/

And I always keep an unmodified 'vanilla' tree from which everything is 
sourced (and hardlinked to).

It's a categorization system, a namespace.  Top-level repositories are 
broad categories, and branches sub-divide those categories.

	Jeff

  reply	other threads:[~2005-06-26 19:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-26 18:15 [PATCH] Add git-relink-script to fix up missing hardlinks Ryan Anderson
2005-06-26 18:36 ` Jeff Garzik
2005-06-26 19:07 ` Junio C Hamano
2005-06-26 19:31   ` Junio C Hamano
2005-06-26 19:44     ` Jeff Garzik [this message]
2005-06-27  1:11       ` Jan Harkes

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=42BF058F.8010301@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=ryan@michonline.com \
    --cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.