-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hithere! #1
Comments
Savages
…On Tue, May 1, 2018, 6:02 AM Simon Rozet ***@***.***> wrote:
[image: screen shot 2018-05-01 at 1 02 14 pm]
<https://user-images.githubusercontent.com/90/39470780-e8ef49e4-4d3f-11e8-86d1-bd368dae01e4.png>
😢
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAAYc4r3b4OrmgnGXGFqzEpYYpXlXOfwks5tuEDSgaJpZM4Hcne7>
.
|
Repository owner
deleted a comment from
kapv89
Jun 21, 2019
Repository owner
deleted a comment from
kapv89
Jun 21, 2019
I mean, in all fairness it was a repeat gif. |
21 tasks
3 tasks
Turns out this was a repeat that got resurrected in notifications and I didn't realize it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
My username on GitHub is @rick. If you have a public GitHub repository and you mention @rick on it, I get notified. People often do this when they're doing things like "Hey @rick Johnson what do you think about frobnitz?", where Rick Johnson is some person within GitHub or email reach of their project or job or whatever.
It's all good. But I'm going to say "hi" to you if you ping me. It's amusing to me the range of responses this elicits.
Some of the old images have bit-rotted, I'm generally better about fully uploading any images these days so that doesn't happen any more. It's more work, but I care about you, the customer.
The text was updated successfully, but these errors were encountered: