9 ms·

You can't stop this without breaking git. There is no master repository in git, where user access can be checked. As far as a git repo is concerned, you could e

by knome 13y ago

You can't stop this without breaking git. There is no master repository in git, where user access can be checked. As far as a git repo is concerned, you could easily be checking in a commit Linus sent you, in which case it would be doing the exactly right thing. If you want confirmation that a certain person has done something in git, you'll have to have them sign the commit in some fashion. github is correcting in politely passing this off as a non-issue.

csmuk 13y ago
This is one of many reasons why we still use SVN. Every commit is authenticated against our LDAP server so is technically signed against a user based on their credentials.
- sandfox 13y ago
  You could (and many) do the same thing with git.
  - deleted 13y ago
    [deleted]
- MetaCosm 13y ago
  ... you can sign your git commits with GPG, which is a hell of a lot better than "technically signed" via random internal LDAP and implied relationships. Git has an intentional separation between author of a commit, and the person who signed-off on it. So if you hired an outside contractor to work a little bit of code, he could write it, send it to you, and then an internal person with a GPG key would review it and sign-off on it. It would retain the original author (contractor) and it would retain the person who put it into your code and "signed off" on it. What other non-reasons do you have for using SVN?
  - jimmaswell 13y ago
    It's a hell of a lot simpler if you don't need a ton of branches, and better integrated with Windows.
    - MetaCosm 13y ago
      There are lots of wonderful integrations / applications for windows now. The days of windows being awful with Git are behind us. Hell of a lot simpler if you don't need ANY branches. Merging is still a goddamn nightmare with SVN.
      - zalew 13y ago
        > There are lots of wonderful integrations / applications for windows now. The days of windows being awful with Git are behind us. Please tell me more, how I can get behind Git being awful on Win7 since I have to use this OS at work (and since I've been on Linux personally for a few years, I have no clue). I have only some crappy git console and my config even doesn't work outside of it. Thank you.
        katbyte 13y ago
        msysgit + tortoise git make it pretty simple, and Visual Studio 2013 has built in git support (however I've not used it very much)
        zalew 13y ago
        I don't use VS, and as it turns out, the crappy console I'm talking about is this msysgit. The lack of a decent consistent terminal is my biggest pain in win7. cmd, powershell, msysgit - they all are total crap and every one works differently. And my Git settings aren't working from Eclipse, basically the only place they work is this git terminal. Sorry, but that's not 'wonderful integration'. On Linux everything just works.
        jimmaswell 13y ago
        Really? In my Linux experience it's a lot more rare for things to 'just work' than on Windows. Windows' homogenous environment contributes to this.
  - csmuk 13y ago
    How many people other than developers can handle GPG? We have office staff, graphic designers, operations and technical authors as well using SVN. About 100 people and several separate repositories. sAMAccountName is passed through transparently from users' NT accounts using NTLM. Relationships are also very strongly enforced with access to their own workstations tied down. Other non reasons: 1. partial checkouts. 2. Easy ACL control. 3. Great tooling for windows 4. Locking (oh the sin) - we have numerous unmergeable binary files like PSDs going in as well. 5. No problems with large bins like reference DLLs and graphics. 6. Bomb proof with a top end repo size of 14G and 100000 revs and NO problems reported. 7. Centralised commit policy. We have scripts that test check ins for stupid things people have done, bad ticket references etc. I could go on. It works very well for us (oh and we don't have merge tracking problems for reference).

by knome 13y ago

csmuk 13y ago

This is one of many reasons why we still use SVN. Every commit is authenticated against our LDAP server so is technically signed against a user based on their credentials.

sandfox 13y ago
You could (and many) do the same thing with git.
- deleted 13y ago
  [deleted]
MetaCosm 13y ago
... you can sign your git commits with GPG, which is a hell of a lot better than "technically signed" via random internal LDAP and implied relationships. Git has an intentional separation between author of a commit, and the person who signed-off on it. So if you hired an outside contractor to work a little bit of code, he could write it, send it to you, and then an internal person with a GPG key would review it and sign-off on it. It would retain the original author (contractor) and it would retain the person who put it into your code and "signed off" on it. What other non-reasons do you have for using SVN?
- jimmaswell 13y ago
  It's a hell of a lot simpler if you don't need a ton of branches, and better integrated with Windows.
  - MetaCosm 13y ago
    There are lots of wonderful integrations / applications for windows now. The days of windows being awful with Git are behind us. Hell of a lot simpler if you don't need ANY branches. Merging is still a goddamn nightmare with SVN.
    - zalew 13y ago
      > There are lots of wonderful integrations / applications for windows now. The days of windows being awful with Git are behind us. Please tell me more, how I can get behind Git being awful on Win7 since I have to use this OS at work (and since I've been on Linux personally for a few years, I have no clue). I have only some crappy git console and my config even doesn't work outside of it. Thank you.
      - katbyte 13y ago
        msysgit + tortoise git make it pretty simple, and Visual Studio 2013 has built in git support (however I've not used it very much)
        zalew 13y ago
        I don't use VS, and as it turns out, the crappy console I'm talking about is this msysgit. The lack of a decent consistent terminal is my biggest pain in win7. cmd, powershell, msysgit - they all are total crap and every one works differently. And my Git settings aren't working from Eclipse, basically the only place they work is this git terminal. Sorry, but that's not 'wonderful integration'. On Linux everything just works.
        jimmaswell 13y ago
        Really? In my Linux experience it's a lot more rare for things to 'just work' than on Windows. Windows' homogenous environment contributes to this.
- csmuk 13y ago
  How many people other than developers can handle GPG? We have office staff, graphic designers, operations and technical authors as well using SVN. About 100 people and several separate repositories. sAMAccountName is passed through transparently from users' NT accounts using NTLM. Relationships are also very strongly enforced with access to their own workstations tied down. Other non reasons: 1. partial checkouts. 2. Easy ACL control. 3. Great tooling for windows 4. Locking (oh the sin) - we have numerous unmergeable binary files like PSDs going in as well. 5. No problems with large bins like reference DLLs and graphics. 6. Bomb proof with a top end repo size of 14G and 100000 revs and NO problems reported. 7. Centralised commit policy. We have scripts that test check ins for stupid things people have done, bad ticket references etc. I could go on. It works very well for us (oh and we don't have merge tracking problems for reference).