You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@Stanzilla we were intentionally secretive about this security bug, to allow all of the various Git implementations to move in unison. I am proud that you detected how hard we worked on protecting the users.
Now that you know just how much was done for you, you might want to step up your efforts to contribute back something of value to this project.
To be honest, the whole Git for/on Windows situation is not really transparent.
Okay, such a negative statement should really be backed up by some positive action, to balance out empathy-wise. You really should help the situation e.g. by writing a FAQ entry, and/or by enhancing the home page with a link to documentation of this project's governance. Any information you need to do that, please just ask away!
I only asked questions, never demanded anything in here. Also you still didn't answer my question if the page is only linking to the wrong repository and should be updated (I would do that, even already forked the repo) or not.
Activity
dscho commentedon Dec 18, 2014
Have you looked at the releases? https://github.com/msysgit/msysgit/releases/tag/Git-1.9.5-preview20141217
dscho commentedon Dec 18, 2014
Assuming that you expected a link to the portable release on https://msysgit.github.io/, I respectfully suggest to clone https://github.com/msysgit/msysgit.github.com/, make the necessary changes, test, and then open a Pull Request.
Stanzilla commentedon Dec 18, 2014
Thanks for the link. So I guess the real bug is that on https://msysgit.github.io/ the "Repository" link points to https://github.com/msysgit/git which does not have the release, no?
dscho commentedon Dec 18, 2014
So it is a bug when not even a full hour after the upload of a new security bug-fix release not all the source is available?
Stanzilla commentedon Dec 18, 2014
No, I understood it that way that we're supposed to check https://github.com/msysgit/msysgit/releases/ instead of https://github.com/msysgit/git/releases
To be honest, the whole Git for/on Windows situation is not really transparent.
dscho commentedon Dec 19, 2014
@Stanzilla we were intentionally secretive about this security bug, to allow all of the various Git implementations to move in unison. I am proud that you detected how hard we worked on protecting the users.
Now that you know just how much was done for you, you might want to step up your efforts to contribute back something of value to this project.
dscho commentedon Dec 19, 2014
Okay, such a negative statement should really be backed up by some positive action, to balance out empathy-wise. You really should help the situation e.g. by writing a FAQ entry, and/or by enhancing the home page with a link to documentation of this project's governance. Any information you need to do that, please just ask away!
Stanzilla commentedon Dec 19, 2014
I'm baffled about the amount of arrogance someone can fit into so few posts so I'm going to pass on that, sorry.
dscho commentedon Dec 19, 2014
@Stanzilla and I am baffled about the arrogance of somebody demanding others to put in effort and then just leaving in a poof.
I guess that leaves two people baffled, one who worked a lot and then another one. I don't know who's more arrogant.
Stanzilla commentedon Dec 19, 2014
I only asked questions, never demanded anything in here. Also you still didn't answer my question if the page is only linking to the wrong repository and should be updated (I would do that, even already forked the repo) or not.
Fix status for old-style submodules with commondir
Fix status for old-style submodules with commondir
Fix status for old-style submodules with commondir
Fix status for old-style submodules with commondir
Fix status for old-style submodules with commondir
Fix status for old-style submodules with commondir
Fix status for old-style submodules with commondir
amend! Add config option `windows.appendAtomically`
amend! Add config option `windows.appendAtomically`
Fix status for old-style submodules with commondir
attr: fix out-of-bounds write when parsing huge number of attributes
pretty: fix out-of-bounds write caused by integer overflow
reftable/reader: introduce refcounting
reftable/reader: introduce refcounting
reftable/reader: introduce refcounting
builtin/history: unuse the commit buffer after use