latest 19 messages by DeHackEd
+
[2015-09-03T12:16:30Z]
DeHackEd
for read access?
+
[2015-09-03T00:32:19Z]
DeHackEd
it's called merging or rebasing, depending on how you want to do it
+
[2015-09-01T21:03:06Z]
DeHackEd
https://github.com/blog/821 <-- the "disabling @mention notifications" section does't seem applicable anymore. i want to disable this without disabling other notification scenarios. anyone know something I don't, or should I open a ticket of sorts?
+
[2015-05-30T20:40:30Z]
DeHackEd
:)
+
[2015-05-30T20:40:28Z]
DeHackEd
I'm finnicky about that
+
[2015-05-30T20:40:16Z]
DeHackEd
true, but they changed something between a blog post and now and the blog post is now inaccurate. (and I liked the blog post's method before)
+
[2015-05-30T20:36:52Z]
DeHackEd
my feature request was related to notifications. the tarball thing was just a bad recollection of the trick
+
[2015-05-30T20:35:38Z]
DeHackEd
no doubt
+
[2015-05-30T20:35:01Z]
DeHackEd
(and this was months ago now)
+
[2015-05-30T20:34:23Z]
DeHackEd
I've submitted my request with the "contact a human" link, does that count or shoudl I still use support?
+
[2015-05-30T20:33:16Z]
DeHackEd
Nevik: be better if what I say was true
+
[2015-05-30T20:32:27Z]
DeHackEd
that trick works for diffs, but not tarballs... the rewrite is different
+
[2015-05-30T20:31:26Z]
DeHackEd
oops, no that doesn't work..
+
[2015-05-30T20:30:55Z]
DeHackEd
add .tar.gz to the end of the URL for it
+
[2015-05-30T18:10:26Z]
DeHackEd
now for my own complaint. apparently github once had the ability to independently block an @mention generating a notification (see https://github.com/blog/821 ) but now it's merged into other notification settings. so is there a way to get that back so an @mention can go ignored all by itself ?
+
[2015-05-30T18:07:28Z]
DeHackEd
also keep in mind that Git does its own checks. the commit is an SHA1 of not only the files, but the complete history. and github will let you check out any commit
+
[2015-05-30T17:18:26Z]
DeHackEd
if SSL is designed to be resistent against a smart, malicious person then it should be resistent against random bitflips due to EMI or something
+
[2015-05-30T17:15:18Z]
DeHackEd
it's designed to be tamper-proof. is that good enough?
+
[2015-05-30T17:12:19Z]
DeHackEd
If you're worried about network corruption or tampering, I thought that SSL/TLS provided integrity of the file in transport.