Re: fatal: Could not get current working directory: Permission denied | affected 2.10,2.11,2.12, but not 1.9.5 |

Od: "René Scharfe" <l.s.r@web.de>
Do: "Zenobiusz Kunegunda" <zenobiusz.kunegunda@interia.pl>; 
Wysłane: 18:59 Wtorek 2017-03-14
Temat: Re: fatal: Could not get current working directory: Permission denied | affected 2.10,2.11,2.12, but not 1.9.5 |

quoted

Am 14.03.2017 um 08:44 schrieb Zenobiusz Kunegunda:
Od: "René Scharfe" <l.s.r@web.de> Do: "Zenobiusz Kunegunda"
<zenobiusz.kunegunda@interia.pl>; Wysłane: 22:31 Poniedziałek
2017-03-13 Temat: Re: fatal: Could not get current working directory:
Permission denied | affected 2.10,2.11,2.12, but not 1.9.5 |

quoted

quoted

Am 13.03.2017 um 14:23 schrieb Zenobiusz Kunegunda: Bisecting: 0
revisions left to test after this (roughly 0 steps)
[a26bc613a64ac2c7ee69a50675e61b004a26382d] pretty.c: make
git_pretty_formats_config return -1 on git_config_string failure

This is what I found with git bisect

Strange, I don't think git_pretty_formats_config() is even called
by git status.

René

a26bc613a64ac2c7ee69a50675e61b004a26382d - is actually working
revision

The question is - is git history linear enough for git bisect to
produce any useful result? Gitk produces rather complicated diagram.
Especially for year 2014. I'm not sure about reliability of this
method. Or maybe it should be used in a specific way I'm not aware
of. If you have any advices how to use it in this specific case,
please let me know.

Ah, right, I didn't pay enough attention, sorry.  Step 0 is the last 
one, but you need to rate it as good or bad before reset presents the 
result.  History is not really linear in git's own repository.  But if 
you didn't reset bisect's status you may still be able to finish it by 
running "git bisect good a26bc613" now.

(And if that doesn't work then at least you now have a much quicker way 
to check using the long directory name..)

René

Oh, my bad. Haven't been using git bisect for quiet a while and forgot to rate.
Ok, so I did bisect again

$ git bisect bad
7333ed1788b4f2b162a35003044d77a716732a1f is the first bad commit
commit 7333ed1788b4f2b162a35003044d77a716732a1f
Author: René Scharfe [off-list ref]
Date:   Mon Jul 28 20:26:40 2014 +0200

    setup: convert setup_git_directory_gently_1 et al. to strbuf
    
    Convert setup_git_directory_gently_1() and its helper functions
    setup_explicit_git_dir(), setup_discovered_git_dir() and
    setup_bare_git_dir() to use a struct strbuf to hold the current working
    directory.  Replacing the PATH_MAX-sized buffer used before removes a
    path length limition on some file systems.  The functions are converted
    all in one go because they all read and write the variable cwd.
    
    Signed-off-by: Rene Scharfe [off-list ref]
    Signed-off-by: Junio C Hamano [off-list ref]

:100644 100644 0a22f8bd1d631fe5f0afe1d84162ca4064a00e4f 937dad503c28681d7c21f5dc300ea943cfe5b17a M	setup.c

$ git bisect log
git bisect start
# bad: [b260d265e189728b26e50506ac6ffab6a7d588da] Git 2.2
git bisect bad b260d265e189728b26e50506ac6ffab6a7d588da
# good: [83332636f575f00edff8f3afb15a2f96885bf417] Git 1.9.5
git bisect good 83332636f575f00edff8f3afb15a2f96885bf417
# good: [9181365b856a63f8c5486ad0fe48f1cd60852da3] Merge branch 'maint-1.8.5' into maint-1.9
git bisect good 9181365b856a63f8c5486ad0fe48f1cd60852da3
# good: [9181365b856a63f8c5486ad0fe48f1cd60852da3] Merge branch 'maint-1.8.5' into maint-1.9
git bisect good 9181365b856a63f8c5486ad0fe48f1cd60852da3
# good: [ba655d15b58ab2a00032b74e5b2617a0b658a01f] Merge branch 'sk/mingw-main'
git bisect good ba655d15b58ab2a00032b74e5b2617a0b658a01f
# bad: [88e7dff93d7010bb2974f8e1599a4e53c73e18f3] Merge branch 'jk/prune-top-level-refs-after-packing'
git bisect bad 88e7dff93d7010bb2974f8e1599a4e53c73e18f3
# good: [8a7b034d6d451491dbcfaebc3d4ed4f08c756822] add tests for `git_config_get_string_const()`
git bisect good 8a7b034d6d451491dbcfaebc3d4ed4f08c756822
# bad: [f655651e09b9fa7bf8ff13f1b4a5b16c7956e4cf] Merge branch 'rs/strbuf-getcwd'
git bisect bad f655651e09b9fa7bf8ff13f1b4a5b16c7956e4cf
# good: [aa544bfbc6eb11e4f0471f3144d3e3ac75c0e4a9] Sync with 2.0.4
git bisect good aa544bfbc6eb11e4f0471f3144d3e3ac75c0e4a9
# good: [212d781c967317a05a704609ddf3ffc8a09f8590] Merge branch 'jk/fix-profile-feedback-build'
git bisect good 212d781c967317a05a704609ddf3ffc8a09f8590
# good: [44ceb79f84b0f339147d2d44e4bb50cc472be03e] Merge branch 'jk/pretty-empty-format'
git bisect good 44ceb79f84b0f339147d2d44e4bb50cc472be03e
# bad: [4d3ab44d26c47d100cec39d0ef9ed9746eb7e454] use xgetcwd() to set $GIT_DIR
git bisect bad 4d3ab44d26c47d100cec39d0ef9ed9746eb7e454
# bad: [251277acdf8c8dee59bdd0e9e7b7e3502226cf9d] abspath: use strbuf_getcwd() to remember original working directory
git bisect bad 251277acdf8c8dee59bdd0e9e7b7e3502226cf9d
# good: [d13a0a97e097c6a601bafc529a716477cc94dc20] unix-sockets: use strbuf_getcwd()
git bisect good d13a0a97e097c6a601bafc529a716477cc94dc20
# bad: [7333ed1788b4f2b162a35003044d77a716732a1f] setup: convert setup_git_directory_gently_1 et al. to strbuf
git bisect bad 7333ed1788b4f2b162a35003044d77a716732a1f
# first bad commit: [7333ed1788b4f2b162a35003044d77a716732a1f] setup: convert setup_git_directory_gently_1 et al. to strbuf