| 1 |
Dnia 2013-08-31, o godz. 06:55:01 |
| 2 |
"C. Bergström" <cbergstrom@×××××××××.com> napisał(a): |
| 3 |
|
| 4 |
> Do you have any plans to add support for sparse checkout? |
| 5 |
> |
| 6 |
> Something like this |
| 7 |
> |
| 8 |
> |cd <parentdir> |
| 9 |
> git clone -n <url> |
| 10 |
> cd <repo_dir> |
| 11 |
> git remote add –f <name> <url> |
| 12 |
> git config core.sparsecheckout true |
| 13 |
> echo /<foldername>/ >> .git/info/sparse-checkout |
| 14 |
> git checkout <tagname> |
| 15 |
|
| 16 |
Considering our specific work flow, I think it would be enough to do: |
| 17 |
|
| 18 |
git checkout <branch> [<dir1> <dir2> ...] |
| 19 |
|
| 20 |
Depending on the need for it, I can either add it as optional arguments |
| 21 |
to git_checkout or an envvar for it. |
| 22 |
|
| 23 |
|
| 24 |
> -------- |
| 25 |
> What about subtrees? |
| 26 |
|
| 27 |
Looking at their specific design, don't they work out-of-the-box? |
| 28 |
|
| 29 |
-- |
| 30 |
Best regards, |
| 31 |
Michał Górny |
Archives