From: Linus Torvalds <torvalds@osdl.org>
To: Alan Chandler <alan@chandlerfamily.org.uk>
Cc: git@vger.kernel.org
Subject: Re: Question around git-shell usage in Everyday Git
Date: Wed, 1 Feb 2006 15:30:35 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0602011523000.21884@g5.osdl.org> (raw)
In-Reply-To: <200602012301.56141.alan@chandlerfamily.org.uk>
On Wed, 1 Feb 2006, Alan Chandler wrote:
>
> My question, in this case is there any reason (such as git creating home
> directoriy temp files or something) why each developer could not have their
> home directory as the root of all the repositories (ie where my git user in
> the above example had its home directory).
No reason why not.
I use my home directory for all _my_ projects, and just clone them within
my own network with
git pull g5:v2.6/linux ..
rather than using the absolute path-name.
And no, git should never use your home directory for anything else (ie
all file operations are normally done just in $GIT_OBJECT_DIR or
similar: some things like "git-diff-files" will use the current working
directory, but nothing uses $HOME (*)).
So I would indeed suggest that the home directory would be the natural
place to put developer projects.
Linus
(*) Not entirely true. "git-cvsimport" uses "$HOME/.cvspass" for CVS
passwords. But the _basic_ git commands shouldn't do that.
prev parent reply other threads:[~2006-02-01 23:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-01 23:01 Question around git-shell usage in Everyday Git Alan Chandler
2006-02-01 23:21 ` Junio C Hamano
2006-02-01 23:30 ` Junio C Hamano
2006-02-01 23:37 ` Linus Torvalds
2006-02-02 0:04 ` Junio C Hamano
2006-02-02 5:17 ` Alan Chandler
2006-02-02 5:44 ` Junio C Hamano
2006-02-02 21:23 ` Alan Chandler
2006-02-01 23:30 ` Linus Torvalds [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.64.0602011523000.21884@g5.osdl.org \
--to=torvalds@osdl.org \
--cc=alan@chandlerfamily.org.uk \
--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.
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).