41–50 of 302 posts
Earlier quoted context omitted.
That does seem like a mistake, upon a cursory examination.
I submitted a PR on github https://github.com/git/git/pull/1235 . Supposedly there's a bot who will send an email, but I don't have permissions to use it... mhm...
Going to send an email the old–fashioned way?
Deep inside some large enterprise company: Jr Engineer: "Hey, I know we've always managed our little dotnet application via email and shared-network-drive, but I've been reading about a thing called "git" that we should probably use." Sr Engineer: "Change is scary and bad, also we are not a software company. We're not going to learn some newfangled whatsit. Just email me the .vba files when you want me to review the…
Deep inside some large enterprise company: Jr Engineer: "Hey, I know we've always managed our little dotnet application via email and shared-network-drive, but I've been reading about a thing called "git" that we should probably use." Sr Engineer: "Change is scary and bad, also we are not a software company. We're not going to learn some newfangled whatsit. Just email me the .vba files when you want me to review the…
The only difference is that my git pitch went really well and they promised they would start using it. They never started using it.
Earlier quoted context omitted.
I submitted a PR on github https://github.com/git/git/pull/1235 . Supposedly there's a bot who will send an email, but I don't have permissions to use it... mhm...
Fun :) Going to send an email the old–fashioned way?
Deep inside some large enterprise company: Jr Engineer: "Hey, I know we've always managed our little dotnet application via email and shared-network-drive, but I've been reading about a thing called "git" that we should probably use." Sr Engineer: "Change is scary and bad, also we are not a software company. We're not going to learn some newfangled whatsit. Just email me the .vba files when you want me to review the…
I feel like this doesn't have much to do with Git specifically. Seems to me like PS1 needs to avoid accessing files that aren't owned by the current user. Easier said than done though...
Ah, so this is why my simple github release action randomly stopped working today... awesome
Earlier quoted context omitted.
Maybe it's intended? If you specify a directory for something in your git config it sounds reasonable to assume you trust it. That said, if it is intended, I'm surprised there isn't a comment mentioning that because it certainly looks like a bug.
I considered that too... but not sure. There's also the fact that it'll reset is_safe to 0 on each config line... which is likely not intended. Seems like a rushed patch. Unless I'm seriously misunderstanding how that read_very_early_config function works (it calls the cb for each key-value pair in the config, I'm assuming).