From: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
To: Matthieu Moy <Matthieu.Moy@imag.fr>
Cc: Jakub Narebski <jnareb@gmail.com>,
"Nguyen Thai Ngoc Duy" <pclouds@gmail.com>,
"git mailing list" <git@vger.kernel.org>
Subject: Re: on subtree checkout
Date: Sun, 24 Feb 2008 18:22:42 +0100 [thread overview]
Message-ID: <200802241822.42594.robin.rosenberg.lists@dewire.com> (raw)
In-Reply-To: <vpqve4efiql.fsf@bauges.imag.fr>
söndagen den 24 februari 2008 skrev Matthieu Moy:
> I suppose you have to forbid merges where anything non-trivial happens
> outside the tree (i.e. allow it only if the set of renamed or changed
> files is disjoint outside the tree, or only if only one of the
> branches to merge have changes outside the tree).
One still has to allow it, maybe forcing a bigger checkout in those
cases.
> That's probably not such a big limitation in practice for the user,
> since by definition the user won't modify the files outside its tree,
> so he can at least still merge with the branch he branched from.
Partial checkout is for convenience and speed of worktree operations as
I see it. Other people could have other reasons for it. Branch switching takes a lot of time with big repos, same thing with git status, add -u etc. Restricting the worktree scan for uninteresting parts speeds things up.
> I can see another problem: partial checkout is really interesting only
> if you can do a partial clone ("partial" here in the sense "subtree").
> Otherwise, your .git/ still eats your disk space and "clone" still
> needs your bandwidth for something you won't use.
Better and more of "global" operations on repos with submodules might make them more bearable, and maybe even convenient, for example doing a git diff
over a set of submodules detecting renames between submodules.
-- robin
next prev parent reply other threads:[~2008-02-24 17:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-24 9:34 on subtree checkout Nguyen Thai Ngoc Duy
2008-02-24 9:59 ` Robin Rosenberg
2008-02-24 10:23 ` Jakub Narebski
2008-02-24 10:53 ` Robin Rosenberg
2008-02-24 11:53 ` Jakub Narebski
2008-02-24 10:03 ` Jakub Narebski
2008-02-24 15:12 ` Nguyen Thai Ngoc Duy
2008-02-24 15:45 ` Jakub Narebski
2008-02-24 15:59 ` Matthieu Moy
2008-02-24 17:22 ` Robin Rosenberg [this message]
2008-02-26 1:59 ` Johannes Schindelin
2008-02-26 2:30 ` David Symonds
2008-02-26 11:23 ` Johannes Schindelin
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=200802241822.42594.robin.rosenberg.lists@dewire.com \
--to=robin.rosenberg.lists@dewire.com \
--cc=Matthieu.Moy@imag.fr \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=pclouds@gmail.com \
/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).