Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Johannes Schindelin
    @dscho
    Not really, it is supposed to resolve symbolic links (i.e. show the real path).
    At least as far as I remember.
    David Macek
    @elieux
    root@6fa410b66046:/www# git -C /src rev-parse --show-toplevel
    /src
    root@6fa410b66046:/www# ln -s /src lol
    root@6fa410b66046:/www# cd lol
    root@6fa410b66046:/www/lol# git rev-parse --show-toplevel
    /src
    Okay.
    Then I need to bring up my issue elsewhere. :)
    Thanks.
    Johannes Schindelin
    @dscho
    You bet.
    David Macek
    @elieux
    Apparently, someone shares my issue: microsoft/vscode#116064
    (Just for reference.)
    Johannes Schindelin
    @dscho
    Yes, it used to be different, but we had to do this in order to become consistent with Linux.
    David Macek
    @elieux
    I guess that was the change I observed.
    David Macek
    @elieux
    @dscho, do you know anything about a bunch of Google Cloud projects with git-for-windows@googlegroups.com as a member?
    image.png
    ... for example.
    Johannes Schindelin
    @dscho
    I did not.
    I cannot see the linked page, though, I do not have permissions.
    David Macek
    @elieux
    I assume you're in that Google group, right?
    Johannes Schindelin
    @dscho
    David Macek
    @elieux
    Weird.
    Do you see any projects in your Cloud console?
    Johannes Schindelin
    @dscho
    Do I have a Cloud console?
    David Macek
    @elieux
    If you have a Google account, yes.
    It may require you to specify few things first.
    Johannes Schindelin
    @dscho
    Wow, I have no idea what I should do there.
    And why I am seeing that project "1234".
    And who this gyg3131 person is.
    David Macek
    @elieux
    So you do see it.
    Okay, at least I'm not alone.
    Maybe you can remove the group from there.
    Johannes Schindelin
    @dscho
    image.png
    Nope.
    David Macek
    @elieux
    Well, then. :D
    Johannes Schindelin
    @dscho
    @elieux FYI I finally managed to rebase Git for Windows' BusyBox-w32 patches to a newer version. There are quite a few hacks still, and I am pretty unsure that I want to keep the \\?\ business (read: I intend to drop it completely), but I managed to compile it here. I pushed up the result as wip-rebase-2021-02-19 to https://github.com/dscho/busybox-w32.
    David Macek
    @elieux
    Ooh. Nice. I should try it. I know of at least one bug in path handling with the current version.
    Johannes Schindelin
    @dscho
    Cool. Maybe you can also help with cleaning up the TO-SPLIT and the Ensure... patches?
    David Macek
    @elieux
    You got a response on that 0-bit relocation.
    Johannes Schindelin
    @dscho
    Yes, and it's a good one.
    David Macek
    @elieux
    Not sure if relevant, but there's a new busybox-w32 release from today.
    Johannes Schindelin
    @dscho
    It is relevant. There are fixes in there that I provided ;-)
    David Macek
    @elieux
    The update-patches.sh scripts in msys2-runtime...
    Nevermind. Now I understand, the first cd is not related to the git repository.
    David Macek
    @elieux
    2.31.0.rc1.windows.1-1 was pulled?
    Johannes Schindelin
    @dscho
    No, why?
    It was superseded by v2.30.2 (which is newer, and "more official").
    David Macek
    @elieux
    Because the supersession is not obvious from the version number.
    Pacman complained that it's a downgrade..
    Anyway, that's enough explanation. Thanks.
    Johannes Schindelin
    @dscho
    But v2.30.2 was superseded by v2.31.0-rc2 (as far as mingw-w64-git goes) in the meantime, anyway...

    Pacman complained that it's a downgrade..

    Oh right, I didn't think of that.