On Sat, Apr 13, 2019 at 10:21:36AM +0100, Klaus Ethgen wrote:
> Finally, the error was a combination of 4 tools, git, vim, the mentioned
> vim-addon and task with a task-hook for committing pending.data.
>
> When I do a git commit which invokes vim, then the following variables
> are set:
> - GIT
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
I did a deep analysis of the problem and found that the trouble finally
was caused of some change in git (I did not search, when this changed.
But maybe you can tell me.)
Finally, the error was a combination of 4 tools, git, vim, the mentioned
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Forgot the link:
[0] https://github.com/farseer90718/vim-taskwarrior
Regards
Klaus
- --
Klaus Ethgen http://www.ethgen.ch/
pub 4096R/4E20AF1C 2011-05-16Klaus Ethgen
Fingerprint: 85D4 CA42 952C 9
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I seems to have found the bug.
My last debugging gave the hint. pending.data is a concept of
taskwarrior and have the .task directory on git control. And I also use
a vim addon for it[0].
It seems that it introduces that troubles. As the last commi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi Christian,
Am Fr den 12. Apr 2019 um 9:39 schrieb Christian Couder:
> On Thu, Apr 11, 2019 at 7:24 PM Klaus Ethgen wrote:
>
> > I am a heavy user of git now at version 2.20.1 on debian.
> >
> > Since some weeks I have the problem that I get of
Hi,
On Thu, Apr 11, 2019 at 7:24 PM Klaus Ethgen wrote:
> I am a heavy user of git now at version 2.20.1 on debian.
>
> Since some weeks I have the problem that I get often "fatal: unable to
> read ..." and a unclear repository after a git commit. The commit itself
> is correct and so a git rese
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi folks,
I am a heavy user of git now at version 2.20.1 on debian.
Since some weeks I have the problem that I get often "fatal: unable to
read ..." and a unclear repository after a git commit. The commit itself
is correct and so a git reset --hard
7 matches
Mail list logo
