Timeline for Allow more than one @name notification per comment
Current License: CC BY-SA 2.5
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 20, 2017 at 10:31 | history | edited | CommunityBot |
replaced http://meta.stackexchange.com/ with https://meta.stackexchange.com/
|
|
| Apr 23, 2014 at 13:38 | history | edited | CommunityBot |
Fixup of bad MSO links to MSE links migration
|
|
| Apr 23, 2014 at 9:13 | history | edited | CommunityBot |
Migration of MSO links to MSE links
|
|
| Feb 4, 2011 at 17:03 | comment | added | Arjan |
True, @Tshepang. Still, in this specific case Sarfraz was the author and hence was notified anyhow. So: no need "to spoil" the one-and-only @ that is at one's disposal on Sarfraz. And hence, in this example, one could indeed us @balpha to notify both him and Sarfraz (when not first using @ to prefix Sarfraz). All this aside: most of the users simply won't know about all these rules, of course. So this is really a workaround.
|
|
| Feb 4, 2011 at 16:41 | comment | added | tshepang | Even if it wasn't directed towards @balpha, it would help if balpha was notified, so that he can e.g. verify/correct the claim. | |
| Apr 2, 2010 at 10:55 | history | edited | Arjan | CC BY-SA 2.5 |
Found a FAQ on the comment replies. Replaced hints with a link.
|
| Apr 2, 2010 at 10:20 | comment | added | dmckee --- ex-moderator kitten | This is the workaround I use. Solves about 90% of cases for me. On the other 10% I either write two comments or just suffer. | |
| Apr 2, 2010 at 10:05 | history | answered | Arjan | CC BY-SA 2.5 |