From: Michael J Gruber <git@drmicha.warpmail.net>
To: Git Mailing List <git@vger.kernel.org>
Subject: Sparse checkout in worktree
Date: Wed, 25 Nov 2015 13:40:09 +0100 [thread overview]
Message-ID: <5655AC29.20801@drmicha.warpmail.net> (raw)
Hi there,
I'm wondering how much it would take to enable worktree specific sparse
checkouts. From a superfluous look:
- $GIT_DIR/info/sparse_checkout needs to be worktree specific
- We don't have much tooling around sparse to speak of at all.
The endgoal would be to have something like
git checkout [--sparse <pattern>]...
which sets up the sparse_checkout file and "git worktree" to pass any
--sparse option on to "git checkout".
While in an ideal world we all have micro repos, in the real world we
often have larger repos with mostly independent subdirs. For a quick fix
on a side branch in a subdir, a new sparse worktree would be an ideal
lean solution.
As it is, "git stash save && git checkout" is leaner but interrupts the
workflow more, and a local "git clone" with links and alternates is
leaner, too, but conceptually overkill if you want to work quickly on an
existing side branch.
Cheers,
Michael
next reply other threads:[~2015-11-25 12:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-25 12:40 Michael J Gruber [this message]
2015-11-25 19:38 ` Sparse checkout in worktree Duy Nguyen
2015-11-25 19:44 ` Michael J Gruber
2015-11-25 20:17 ` Duy Nguyen
2015-11-25 20:44 ` Michael J Gruber
2015-11-25 20:50 ` Duy Nguyen
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=5655AC29.20801@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--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