Hi Bret,
On Wed, 29 May 2019, Bret Barkelew wrote:
> I know it's an incredibly late reply, but I have not seen this issue
> reappear since the patches. Thank you very much for helping!
It might be late, but it is even more welcome! Thanks for the feedback
(and I am particularly happy that it wor
I know it's an incredibly late reply, but I have not seen this issue
reappear since the patches. Thank you very much for helping!
- Bret
On Sat, Apr 27, 2019 at 4:20 PM Johannes Schindelin
wrote:
>
> Hi Bret,
>
> On Thu, 18 Apr 2019, Bret Barkelew wrote:
>
> > This issue is now being reported by
Hi Bret,
On Thu, 18 Apr 2019, Bret Barkelew wrote:
> This issue is now being reported by more users inside MS. I'll also
> reach out to the Git for Windows advocacy group to see if they have
> any ideas.
>
> I have not had time to figure out the inner workings of Tcl/Tk. Is
> there any way to tur
This issue is now being reported by more users inside MS. I'll also
reach out to the Git for Windows advocacy group to see if they have
any ideas.
I have not had time to figure out the inner workings of Tcl/Tk. Is
there any way to turn on tracing/logging in Git for which commands are
being called
On Thu, Jan 10, 2019 at 7:20 AM Johannes Schindelin
wrote:
>
> Hi Bret,
>
> in that case, please try to find a way to trace the commands in a Tcl/Tk
> program (which gitk is) and see which command triggers the error.
Er... that's a little out of my depth. I'll see if I can find time to learn.
Mea
Hi Bret,
in that case, please try to find a way to trace the commands in a Tcl/Tk
program (which gitk is) and see which command triggers the error.
Ciao,
Johannes
On Wed, 9 Jan 2019, Bret Barkelew wrote:
> Will try to reply in-line, when appropriate.
> The latest snapshot (git version 2.20.1.w
Will try to reply in-line, when appropriate.
The latest snapshot (git version 2.20.1.windows.1.5.g6b286585b1) still
has the issue.
- Bret
On Wed, Jan 9, 2019 at 10:39 AM Johannes Schindelin
wrote:
>
> Hi Bret,
>
>
> On Thu, 3 Jan 2019, Bret Barkelew wrote:
>
> > They are the exact same path (wi
Hi Bret,
On Thu, 3 Jan 2019, Bret Barkelew wrote:
> They are the exact same path (with a different drive letter).
[it's a bit hard to follow the thread if you top-post a reply to an
inline-replied answer, maybe imitate the style of other mails in the
future.]
> Another thing I've been able to
They are the exact same path (with a different drive letter).
Another thing I've been able to confirm is I uninstalled git 2.20.1
and installed 2.19.0 on the failing system, and the older version of
Git works.
I've also tried a suggested fix I saw elsewhere to enable long path
names in the Windows
When I open gitk in a particular repository under this version of Git
for Windows, I now get a dialog box that says "Error: couldn't execute
"git": file name too long". I've noticed that the most pronounced
effect is that I cannot see the file diffs (or sometimes the file name
list) for any of the
10 matches
Mail list logo
