> On Tue, Jan 30, 2018 at 9:25 AM, Jessie Hernandez
> wrote:
>>> The sparse-checkout file is specific to each worktree, which allows you
>> to control "sparsity" on a worktree by worktree basis. Therefore, you
>> should create $GIT_DIR/worktrees//info/spars
> On Wed, Jan 24, 2018 at 11:11 AM, Jessie Hernandez
> wrote:
>> I am trying to get a sparse checkout in a linked worktree but cannot
get
>> it working. I have tried the following
>> * git worktree add /some/new/path/new-branch --no-checkout
>> * git c
Hi All,
I am trying to get a sparse checkout in a linked worktree but cannot get
it working. I have tried the following
* git worktree add /some/new/path/new-branch --no-checkout
* git config core.sparseCheckout true
*
* cd /some/new/path/new-branch
* git read-tree -mu sparse-checkout
But I st
subscribe git
> On Mon, Apr 03, 2017 at 10:54:38PM -0400, Jeff King wrote:
>
>> If we declared 7.16.0 as a cutoff, we could unconditionally define
>> USE_CURL_MULTI, which gets rid of quite a few messy ifdefs.
>
> That version came out 11 years ago. Here's what that patch would look
> like (on top of my other on
> On Fri, 31 Mar 2017 09:53:38 +0200
> "Jessie Hernandez" wrote:
>
> [...]
>> >> It's possible to have ttk with 8.5 as well (say, here on Debian 8.5
>> >> ships with ttk enabled).
>> >>
>> >> A proper patch would
>> On Fri, 31 Mar 2017 08:44:27 +0200
>> "Jessie Hernandez" wrote:
>>
>> [...]
>>> I also got this problem when I wanted to build and run git 2.10.x.
>>> I have added the following change to git-gui/git-gui.sh
>>>
>>> di
> On Fri, 31 Mar 2017 08:44:27 +0200
> "Jessie Hernandez" wrote:
>
> [...]
>> I also got this problem when I wanted to build and run git 2.10.x.
>> I have added the following change to git-gui/git-gui.sh
>>
>> diff --git a/git-gui/git-gui.sh b/gi
i.usettk) 0
set default_config(gui.warndetachedcommit) 1
set default_config(gui.tabsize) 8
set font_descs {
If you guys want I can submit it as a patch.
But i assume that 'fixing' this by disabling the feature is not really
what we want.
-
Jessie Hernandez
> --
> David Shrader
> HPC-ENV High Performance Computer Systems
> Los Alamos National Lab
> Email: dshrader lanl.gov
>
>
> On 2017-02-22 06:59 AM, Jessie Hernandez wrote:
>>> HI,
>>>
>>> the reason why it is fixed, is because commit messages should be
>>> wrapped at 76 characters to be used in mails. So it helps you with the
>>> wrapping.
>>>
>>>
.
Thank you for this.
Regards
-----
Jessie Hernandez
>
>
> On Wed, Feb 22, 2017 at 10:27 AM, Jessie Hernandez
> wrote:
>> Hi all,
>>
>> I have been using git for a few years now and really like the software.
>> I have a small annoyance and was wo
if that is necessary or if
something is not clear.
Thank you.
-
Jessie Hernandez
I have tried all of that.
A colleague looked at it and he reset xrdb with xrdb -remove -all
apparently this works and my issues has been fixed.
Regards,
On Wed, Jul 27, 2016 at 10:21 AM, Trần Ngọc Quân wrote:
> On 27/07/2016 15:05, jessie hernandez wrote:
>> Dear git,
>>
>>
attached image).
My OS is Red Hat 6.6
git version is 2.0.3 (i tried the 2.9.2 version also and this too
gives the same small font)
I am running in bash also tried in KSH
Could you give an insight if this is a known gitk issue or that this is a bug?
Regards,
Jessie Hernandez
14 matches
Mail list logo