From: Matthieu Moy <Matthieu.Moy@imag.fr>
To: git@vger.kernel.org
Subject: Re: .gitlink for Summer of Code
Date: Mon, 26 Mar 2007 21:49:30 +0200 [thread overview]
Message-ID: <vpqodmfss39.fsf@olympe.imag.fr> (raw)
In-Reply-To: <200703262133.44520.Josef.Weidendorfer@gmx.de> (Josef Weidendorfer's message of "Mon\, 26 Mar 2007 21\:33\:44 +0200")
Josef Weidendorfer <Josef.Weidendorfer@gmx.de> writes:
> This would work. However, you can not clone from an almost empty .git
> directory with current git.
Of course not. If you say "have .git/ <=> is a repository", then your
lightweight checkout should not have a .git/. But why should anything
that have a .git/ directory be a repository??
> The original proposal was to have a standard .git directory for every
> light-weight checkout inside of the base .git directory, e.g.
> in <base>/.git/ext/<name>.git where <name> is some identifier for the
> lightweight checkout, either provided in the .gitlink file or
> automatically determined.
That seems really weird. That implies for example:
* Deleting a checkout means deleting both your local tree _and_ a part
of the .git/ directory of the repository. Have you ever imagined
having to do more than "rm -fr working-tree" even with an inferior
VCS such as CVS?
* It makes it impossible to have a checkout of a read-only location.
For example, if one of my colleague has a repository in
/home/otheruser/repo/, if I want to get a working tree of it, I need
to get a complete clone of his repo to be able to do it. Assuming
someone ever implements a "lightweight checkout of a remote
location" (bzr has this for example. You can run
"bzr checkout --lightweigth http://whatever.com/), this would mean
creating a directory on the server for each of the potential
clients, not to mention the impossibility to do it over http.
* You have to manage a name for each lightweight checkout. What would
be such name? User-provided? uuidgen-like?
I find the way bzr deals with this pretty elegant: a repository with a
working tree is just a working tree and a repository located in the
same directory. The repository stores its files (content of each
revisions in history, ...) in .bzr/repository/, and the working tree
stores them (the index, pending merges, ... and pointer to the
corresponding branch) in .bzr/checkout/.
--
Matthieu
next prev parent reply other threads:[~2007-03-26 19:49 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-25 12:30 .gitlink for Summer of Code Eric Lesh
2007-03-25 15:20 ` Matthieu Moy
2007-03-25 20:39 ` Shawn O. Pearce
2007-03-25 20:54 ` Johannes Schindelin
2007-03-25 21:03 ` Shawn O. Pearce
2007-03-25 20:55 ` Junio C Hamano
2007-03-25 21:05 ` Shawn O. Pearce
2007-03-27 3:40 ` Petr Baudis
2007-03-26 17:16 ` Eric Lesh
2007-03-26 17:22 ` Matthieu Moy
2007-03-26 17:38 ` Eric Lesh
2007-03-26 18:35 ` Martin Waitz
2007-03-26 19:33 ` Josef Weidendorfer
2007-03-26 19:49 ` Matthieu Moy [this message]
2007-03-26 23:14 ` Josef Weidendorfer
2007-03-27 16:59 ` Matthieu Moy
2007-03-26 22:03 ` Martin Waitz
2007-03-26 22:51 ` Junio C Hamano
2007-03-26 23:16 ` Submodule object store Martin Waitz
2007-03-26 23:28 ` Junio C Hamano
2007-03-26 23:36 ` Martin Waitz
2007-03-26 23:20 ` David Lang
2007-03-26 23:55 ` Martin Waitz
2007-03-26 23:40 ` David Lang
2007-03-27 15:25 ` Martin Waitz
2007-03-27 16:53 ` David Lang
2007-03-27 0:29 ` Junio C Hamano
2007-03-27 14:28 ` Martin Waitz
2007-03-27 11:25 ` Uwe Kleine-König
2007-03-27 11:50 ` Uwe Kleine-König
2007-03-27 15:53 ` Martin Waitz
2007-03-27 16:56 ` Josef Weidendorfer
2007-03-27 16:44 ` Martin Waitz
2007-03-27 17:22 ` Uwe Kleine-König
2007-03-27 18:41 ` Linus Torvalds
2007-03-27 19:42 ` Uwe Kleine-König
2007-03-27 19:53 ` Linus Torvalds
2007-03-27 19:59 ` Linus Torvalds
2007-03-27 15:46 ` Martin Waitz
2007-03-26 23:17 ` .gitlink for Summer of Code Josef Weidendorfer
[not found] ` <Pine.LNX.4.64.0703270952020. 6730@woody.linux-foundation.org>
2007-03-26 23:24 ` Junio C Hamano
2007-03-27 17:04 ` Linus Torvalds
2007-03-27 17:00 ` David Lang
2007-03-27 18:15 ` Linus Torvalds
2007-03-27 17:35 ` Martin Waitz
2007-03-27 18:09 ` Daniel Barkalow
2007-03-27 18:19 ` Linus Torvalds
2007-03-27 20:54 ` Daniel Barkalow
2007-03-27 21:11 ` Linus Torvalds
2007-03-27 20:54 ` David Lang
2007-03-27 23:31 ` Jakub Narebski
2007-03-27 23:20 ` David Lang
2007-03-27 18:36 ` Steven Grimm
2007-03-27 20:02 ` Daniel Barkalow
2007-03-27 21:27 ` Linus Torvalds
2007-03-26 23:00 ` Josef Weidendorfer
2007-03-26 23:27 ` Martin Waitz
2007-03-26 17:31 ` Jakub Narebski
2007-03-26 18:21 ` Matthieu Moy
2007-03-27 0:48 ` Jakub Narebski
2007-03-25 20:46 ` Shawn O. Pearce
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=vpqodmfss39.fsf@olympe.imag.fr \
--to=matthieu.moy@imag.fr \
--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).