On Wed, Nov 25, 2015 at 9:44 PM, Michael J Gruber
wrote:
> OTOH, config is common: core.sparseCheckout
> So, the per worktree "switch" is the presence of the sparse-checkout file.
Oh.. but yeah, splitting config file per worktree is on my todo list.
Or you can help finish it [1] if you want to ma
Duy Nguyen venit, vidit, dixit 25.11.2015 21:17:
> On Wed, Nov 25, 2015 at 8:44 PM, Michael J Gruber
> wrote:
>> Duy Nguyen venit, vidit, dixit 25.11.2015 20:38:
>>> On Wed, Nov 25, 2015 at 1:40 PM, Michael J Gruber
>>> wrote:
Hi there,
I'm wondering how much it would take to enabl
On Wed, Nov 25, 2015 at 8:44 PM, Michael J Gruber
wrote:
> Duy Nguyen venit, vidit, dixit 25.11.2015 20:38:
>> On Wed, Nov 25, 2015 at 1:40 PM, Michael J Gruber
>> wrote:
>>> Hi there,
>>>
>>> I'm wondering how much it would take to enable worktree specific sparse
>>> checkouts. From a superfluou
Duy Nguyen venit, vidit, dixit 25.11.2015 20:38:
> On Wed, Nov 25, 2015 at 1:40 PM, Michael J Gruber
> wrote:
>> 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
On Wed, Nov 25, 2015 at 1:40 PM, Michael J Gruber
wrote:
> 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
It already is.
> - We don't have much tooling a
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 chec
6 matches
Mail list logo