From: Krish Jain <krishjain02939@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-staging@lists.linux.dev
Subject: Re: [PATCH] Fix formatting for file "hsdma-mt7621.c"
Date: Fri, 3 Sep 2021 17:30:00 +0200 [thread overview]
Message-ID: <CAPGkw+x7oXb2Wrj79O1o0WYhtbqQPDmSTVGuWdxnV3UuAKFZPg@mail.gmail.com> (raw)
In-Reply-To: <YTG/jv1bZUpDOrh4@kroah.com>
On Fri, Sep 3, 2021 at 8:24 AM Greg KH <gregkh@linuxfoundation.org> wrote:
>
> A: http://en.wikipedia.org/wiki/Top_post
> Q: Were do I find info about this thing called top-posting?
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> A: Top-posting.
> Q: What is the most annoying thing in e-mail?
>
> A: No.
> Q: Should I include quotations after my reply?
>
> http://daringfireball.net/2007/07/on_top
>
> On Thu, Sep 02, 2021 at 10:24:47PM +0200, Krish Jain wrote:
> > Hi, I use nano. I don't see my editor asking me to wrap the changelog
> > text? What exactly can I do to get it properly line wrapped properly?
>
> If you have an editor that is not set up to wrap your lines at 72
> columns, then you need to do it "by hand".
>
> thanks,
>
> greg k-h
Ok, doing that right now. And sorry about top posting, you know it
takes a while till a habit goes away. On autopilot mode, I just am
used to writing on top.
Best Regards
next prev parent reply other threads:[~2021-09-03 15:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-02 11:13 [PATCH] Fix formatting for file "hsdma-mt7621.c" Krish Jain
2021-09-02 9:09 ` Greg KH
2021-09-02 20:24 ` Krish Jain
2021-09-03 6:24 ` Greg KH
2021-09-03 15:30 ` Krish Jain [this message]
2021-09-03 15:49 ` Krish Jain
2021-09-03 17:11 ` Greg KH
2021-09-03 18:54 ` Krish Jain
2021-09-04 6:02 ` Greg KH
2021-09-04 11:11 ` Krish Jain
-- strict thread matches above, loose matches on Subject: below --
2021-09-02 11:11 Krish Jain
2021-09-01 21:37 ` Krish Jain
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPGkw+x7oXb2Wrj79O1o0WYhtbqQPDmSTVGuWdxnV3UuAKFZPg@mail.gmail.com \
--to=krishjain02939@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-staging@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.