git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Dave Jones <davej@redhat.com>, Git Mailing List <git@vger.kernel.org>
Subject: Re: The big git command renaming..
Date: Fri, 29 Apr 2005 16:09:16 -0700	[thread overview]
Message-ID: <4272BE9C.7090906@zytor.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0504291511410.18901@ppc970.osdl.org>

Linus Torvalds wrote:
> 
> Sure. 
> 
> Just a quick question: what are the "rules" for /pub/scm/git? 
> 
> Should I put just git in it, or is it meant for any "git project", and
> should I also copy the 2.6.x kernel home from
> 
> 	/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
> 
> to
> 
> 	/pub/scm/git/linux-2.6.git
> 
> or what?
> 
> Me, I can do either or both, I just don't know what the intent was..

/pub/scm/git I created for your git project; don't move the kernel in there.

If you have any other non-kernel git projects, just let me know and I'll 
make directories for them.

	-hpa

P.S. Are you still updating the trees in 
/pub/linux/kernel/people/torvalds/?  They still show up on our change 
reports, and cause problems for the mirrors.  Perhaps you could replace 
those trees with symlinks into /pub/scm.

	-hpa



  reply	other threads:[~2005-04-29 23:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-29 21:24 The big git command renaming Linus Torvalds
2005-04-29 21:35 ` Dave Jones
2005-04-29 21:58   ` H. Peter Anvin
2005-04-29 22:14     ` Linus Torvalds
2005-04-29 23:09       ` H. Peter Anvin [this message]
2005-04-29 23:39         ` Linus Torvalds
2005-04-29 23:42           ` H. Peter Anvin
2005-04-29 21:41 ` [PATCH] The big git command renaming fallout fix Junio C Hamano
2005-04-29 21:53   ` [PATCH] Makefile: " Junio C Hamano
2005-04-30 14:24 ` The big git command renaming Nicolas Pitre

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=4272BE9C.7090906@zytor.com \
    --to=hpa@zytor.com \
    --cc=davej@redhat.com \
    --cc=git@vger.kernel.org \
    --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 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).