git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jan Harkes <jaharkes@cs.cmu.edu>
To: git@vger.kernel.org
Subject: Re: [PATCH] Add git-relink-script to fix up missing hardlinks
Date: Sun, 26 Jun 2005 21:11:13 -0400	[thread overview]
Message-ID: <20050627011113.GA26049@delft.aura.cs.cmu.edu> (raw)
In-Reply-To: <42BF058F.8010301@pobox.com>

On Sun, Jun 26, 2005 at 03:44:15PM -0400, Jeff Garzik wrote:
> 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/

I actually have been using subdirectories in refs/heads with quite a bit
of success. All of the core tools have no problem with them and only
gitweb and gitk need some small changes to show them correctly.

The subdirectories in refs/heads are user specific in my case, this end
up being pretty useful when combined with Coda's directory ACLs, each
user can maintain their own branches, but cannot modify anyone elses.
All developers have insert, read and lookup rights on the main objects
repository, they can add new objects, but not remove or overwrite any
existing ones.

My branch names end up looking something like 'jaharkes/wdonly',
'awolbach/expand', etc. and it works like a charm.

Jan

      reply	other threads:[~2005-06-27  1:04 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
2005-06-27  1:11       ` Jan Harkes [this message]

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=20050627011113.GA26049@delft.aura.cs.cmu.edu \
    --to=jaharkes@cs.cmu.edu \
    --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).