search for: netiquette

On 12/01/2018 05:49 PM, Ralph Seichter wrote: > * Michael A. Peters: > >> Netiquette posts are just someone's opinion, and they often don't take >> into account the vastly different way different types of minds work. > > Mailing list netiquette has been around for decades, for good reasons. > If Joe User's mind "works differently", Joe needs to...

...the > reply-to-list' option. And that there are mailing list programs that > do not provide the proper list-headers to indicate the mailing list > address. > The problem though is that then muscle memory with keyboard shortcuts result in reply going to the user instead of list. Netiquette posts are just someone's opinion, and they often don't take into account the vastly different way different types of minds work. Just as an example, I have a deaf friend who hates bottom posting because the way captions always work is equivalent to top posting - new content pops up abov...

...crap included. Mikhail Utin ________________________________ From: CentOS <centos-bounces at centos.org> on behalf of Nicolas Kovacs <info at microlinux.fr> Sent: Friday, February 2, 2018 04:36 To: centos at centos.org Subject: [CentOS] Slightly OT : newsletters, mail formatting and netiquette Hi, This question is not exactly CentOS-related strictly speaking, but here goes. I'm running a few newsletter servers for myself and a handful of clients on public CentOS servers with PHPList. For the last twenty years or so I've followed the basic rule that mails should have no formatt...

...here goes. I'm running a few newsletter servers for myself and a handful of clients on public CentOS servers with PHPList. For the last twenty years or so I've followed the basic rule that mails should have no formatting whatsoever, only simple text. And now I wonder if that basic rule of netiquette also applies to newsletters. I'm a subscriber to a series of tech-related newsletters, and I couldn't help but notice that they all seem to be HTML-formatted, even those from respectable hardcore geek groups. So my somewhat naive question: is HTML formatting acceptable in newsletters? Ch...

...g 1% will have to adopt. Just my 2 satang. -----Original Message----- From: asterisk-users-bounces at lists.digium.com [mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Philipp Kempgen Sent: Montag, 08. September 2008 19:22 To: Asterisk Users Subject: [asterisk-users] [OT] email netiquette (was: Re: Re: Asterisk realtime MySQL clients from same IP problem) Patrick Maartense schrieb: > Don't bash MS, I used to bash MS simply because it was MS, but I stopped wasting my time. Now I bash not following email netiquette (RFC 1855 etc.)[1] and in my experience 99 % of all mail pro...

...ing a few newsletter servers for myself and a handful of > clients on public CentOS servers with PHPList. > > For the last twenty years or so I've followed the basic rule that mails > should have no formatting whatsoever, only simple text. And now I wonder > if that basic rule of netiquette also applies to newsletters. > > I'm a subscriber to a series of tech-related newsletters, and I couldn't > help but notice that they all seem to be HTML-formatted, even those from > respectable hardcore geek groups. > > So my somewhat naive question: is HTML formatting ac...

...ext of a message, it probably won't be able to display a log file either. Put another way, would you want the NUT drivers to be written with the same level of care as is evident in most emails sent from a PDA? [*] http://en.wikipedia.org/wiki/Top_posting#Top-posting In lieu of a more official netiquette guide for the NUT lists: * Trim excess quoted text * Insert your reply in between relevant quoted text, or delete everything and add your own context * Make sure you mention which UPS(es) and/or OS you are referring to - especially if your email client hides the subject line, like Gmail's we...

What is the proper netiquette of monitoring a router? How often is often enough verses too often? How large should the monitoring probes be? Is there an aggregate speed (bps) or amount (pps) or both (bps and pps) that should not be exceeded? Grant. . . .

Hi folks, I''ve noticed in recent times on the list that we seem to be getting a low signal-to-noise ratio with a lot of posts (particularly those where people include their configuration). Once you have posted the appropriate information once, there is no need to keep quoting it unless it is central to the discussion. Trimming irrelevant material makes it easy for people who have been

Gentle susbscribers, This is a reminder to all samba mailing list subscribers that this list is moderated. Most of you know what that means, so for the benefit of those who are new to the list or who are not familiar with the mechanics of a mailing list please note the following: 1) Incoming messages are scanned and filtered by mailman to remove messages that may have objectionable content, are

If you must use an out-of-office feature in your email, please exclude any mailing lists you're subscribed to. I deleted the message that I was forwarding in this, but I'm sure we all know what I'm talking about. Tim Conway Unix System Administration Contractor - IBM Global Services desk:3032734776 conway@us.ibm.com

...someone get's it wrong? Apart from the situation that people send mails over the mailing list with "for X.Y." in the subject and no one knows how private that should be. Obviously, it's absolutely not private because it goes to - at least - all folks on the mailing list. > If netiquette is why that sometimes fails, then netiquette does not > match common usage and is the problem. The netiquette is more than just a piece of "documentation of most of the people think how it should work". Please bring serious an factual problems with the netiquette as such and not just...

...this discrepancy, ala >} <Support/hash_set>. >} >Um...was it entirely necessary to issue *8* email messages to the group >with mostly single-line fixes instead of just one email with all of the >fixes and an explanation for each? > > > Actually, yes it was. Proper netiquette when submitting to a technical list is to have a single topic per message. This makes it easy to track issues individually, without the messiness that occurs from bundling several issues together in a single missive. One large email with a big lump of diffs is much less clear, and takes subst...

...gt; Apart from the situation that people send mails over the mailing list > with "for X.Y." in the subject and no one knows how private that should > be. Obviously, it's absolutely not private because it goes to - at least > - all folks on the mailing list. > > > If netiquette is why that sometimes fails, then netiquette does not > > match common usage and is the problem. > The netiquette is more than just a piece of "documentation of most of > the people think how it should work". > > Please bring serious an factual problems with the netique...

...ding on changing load balancing requirements and conditions over time) also change. |>> > I am not subscribed to the list, so I would appreciate being copied on |>> > your responses to the list. | |> |> Tough. You ask here, you hear here. Thank you for your suggestion on netiquette, but I quote from the mailing list home page at http://lists.shorewall.net: " To post to the list, post to shorewall-users@lists.shorewall.net. IMPORTANT: If you are not subscribed to the list, please say so -- otherwise, you will not be included in any replies." Now, does anybody else...

...paravirt_types.h | 32 +++++++++++++++++++++++---- > 1 file changed, 28 insertions(+), 4 deletions(-) More missed feedback: https://lkml.kernel.org/r/CAJcbSZG-JhBC9b1JMv1zq2r5uRQipYLtkNjM67sd7=eqy_iOaA at mail.gmail.com -- Regards/Gruss, Boris. https://people.kernel.org/tglx/notes-about-netiquette

...BUG_ON(sizeof(struct vmcb_save_area) != 1032); > BUILD_BUG_ON(sizeof(struct vmcb_control_area) != 256); > + BUILD_BUG_ON(sizeof(struct ghcb) != 4096); Could those naked numbers be proper, meaningfully named defines? -- Regards/Gruss, Boris. https://people.kernel.org/tglx/notes-about-netiquette

...fdeffery above... > +#endif > + > + /* Initialize IDT descriptor and load IDT */ > + early_idt_descr.address = (unsigned long)idt; > + native_load_idt(&early_idt_descr); > +} > -- > 2.28.0 > -- Regards/Gruss, Boris. https://people.kernel.org/tglx/notes-about-netiquette

...BUG_ON(sizeof(struct vmcb_save_area) != 1032); > BUILD_BUG_ON(sizeof(struct vmcb_control_area) != 256); > + BUILD_BUG_ON(sizeof(struct ghcb) != 4096); Could those naked numbers be proper, meaningfully named defines? -- Regards/Gruss, Boris. https://people.kernel.org/tglx/notes-about-netiquette

...fdeffery above... > +#endif > + > + /* Initialize IDT descriptor and load IDT */ > + early_idt_descr.address = (unsigned long)idt; > + native_load_idt(&early_idt_descr); > +} > -- > 2.28.0 > -- Regards/Gruss, Boris. https://people.kernel.org/tglx/notes-about-netiquette