Re: fatal: unable to read after commit - deeper analysis

. Regards Klaus - -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16 Klaus Ethgen Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C -BEGIN PGP SIGNATURE- Comment: Charset: ISO-8859-1 iQGzBAEBCgAdFi

Re: fatal: unable to read after commit

-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

Re: fatal: unable to read after commit

commit is from 2016, it is very strange. Especially as I had that troubles not before. Regards Klaus - -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16Klaus Ethgen Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C

Re: fatal: unable to read after commit

-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 hav

fatal: unable to read after commit

git reset --hard helps to fix the issue. Any Idea what could be the reason for that problem. I encounter it on different repositories so not limited to one. Any hint how to find out the reason? Regards Klaus Ps. I am not subscribet to the list, so please keep me in the response. - -- Kl

Re: [BUG] Colon in remote urls

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, Am Mo den 12. Dez 2016 um 12:03 schrieb Johannes Schindelin: > On Sun, 11 Dec 2016, Klaus Ethgen wrote: > > Am Sa den 10. Dez 2016 um 19:18 schrieb Johannes Schindelin: > > > On Sat, 10 Dec 2016, Klaus Ethgen wrote: > &g

Re: [BUG] Colon in remote urls

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, Am Sa den 10. Dez 2016 um 19:18 schrieb Johannes Schindelin: > On Sat, 10 Dec 2016, Klaus Ethgen wrote: > > Am Fr den 9. Dez 2016 um 22:32 schrieb Johannes Sixt: > > > There are too many systems out there that use a backslas

Re: [BUG] Colon in remote urls

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Am Sa den 10. Dez 2016 um 11:26 schrieb Jeff King: > On Sat, Dec 10, 2016 at 10:41:33AM +0100, Klaus Ethgen wrote: > > > Am Sa den 10. Dez 2016 um 9:26 schrieb Jeff King: > > > Yeah, I picked it arbitrarily as the common quo

Re: [BUG] Colon in remote urls

to push to two locations at the same time, so why is there > > splitting at all? > > Because the new quarantine feature[1] is built on top of the existing > alternates mechanism, which can have several sources. I'll clone the repo and read about, thanks for the pointer.

Re: [BUG] Colon in remote urls

0_05:00:01.372037552 [...] Compared to the backslash, although it is a perfect legal character in POSIX file systems, I do not know any use of it. Regards Klaus - -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16Klaus Ethgen Fi

Re: [BUG] Colon in remote urls

le name. Regads Klaus - -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16 Klaus Ethgen Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C -BEGIN PGP SIGNATURE- Comment: Charset: ISO-8859-1 iQGzBAEB

Re: [BUG] Colon in remote urls

i.e. GIT_OBJECT_QUARANTINE_DIRECTORY, whose value is > added without splitting to the list of alternate object stores, and > the quarantine codepath can export that instead. I didn't get it, why is there a need to split? I mean, it is not possible to push to two locations at the same tim

[BUG] Colon in remote urls

'/home/xxx:yyy.git' Prepending the path with "file://" does not help. It seems that the new git version splits the url at ":" which ends in two incorrect paths. Pull seems tho work well currently. Regards Klaus Ps. I am not subscribet to the mailing list, so plea