From: Sumitra Sharma <sumitraartsy@gmail.com>
To: Julia Lawall <julia.lawall@inria.fr>
Cc: outreachy@lists.linux.dev
Subject: Re: [PATCH] Staging: qlge: Fix indentation in conditional statement
Date: Sun, 12 Mar 2023 08:27:01 -0700 [thread overview]
Message-ID: <20230312152701.GA28100@ubuntu> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2303121412090.2865@hadrien>
On Sun, Mar 12, 2023 at 02:21:56PM +0100, Julia Lawall wrote:
>
>
> On Sun, 12 Mar 2023, Sumitra Sharma wrote:
>
> > Hi julia,
> >
> > >> Hi julia
> > >>
> > >> I was referring to the reply you sent in this thread and asking to quote
> > >> the most relevant information in the mails so that people on the list
> > >> can know what is being discussed. And I will take care of this in my
> > >> upcoming mails.
> > >>
> > >
> > > Sorry to press the point, but you should be doing it now, not promising to
> > > do it in the future.
> > >
> >
> > I am sorry for repeating my mistake again and again and may be this time
> > too. But, I am trying to correct it.
> >
> > >
> > > If there is some challenge in doing this, please let us know, and perhaps someone can offer some advice.
> > >
> >
> > To be honest I am struggling responding inline. Right now I did it
> > maually by pasting your message into mutt and putting the ">" things. I
> > know this is not the correct way to do. Please guide me to the correct method of responding inline.
>
> I don't use either gmail or mutt, so I'm not an expert. But to interact
> with others about your patches, you will have to solve this problem.
>
> You should be able to receive messages in mutt. There is some information
> in the Outreachy first patch tutorial:
>
> https://kernelnewbies.org/Outreachyfirstpatch
>
> The following link may be useful:
>
> https://www.makeuseof.com/install-configure-mutt-with-gmail-on-linux/
>
> Once your mail arrives in mutt, you should just be able to respond to
> other people and have the >s in front of what they said directly.
>
> julia
Thank you julia for your help. I am now able to respond inline.
Regards,
Sumitra
next prev parent reply other threads:[~2023-03-12 15:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-11 15:24 [PATCH] Staging: qlge: Fix indentation in conditional statement Sumitra Sharma
2023-03-11 16:58 ` Dan Carpenter
2023-03-11 17:28 ` Sumitra Sharma
2023-03-11 18:12 ` Julia Lawall
2023-03-12 6:48 ` Sumitra Sharma
2023-03-12 7:07 ` Julia Lawall
2023-03-12 7:35 ` Sumitra Sharma
2023-03-12 7:45 ` Julia Lawall
2023-03-12 12:29 ` Sumitra Sharma
2023-03-12 13:21 ` Julia Lawall
2023-03-12 15:27 ` Sumitra Sharma [this message]
2023-03-12 15:31 ` Julia Lawall
2023-03-12 15:52 ` Sumitra Sharma
2023-03-12 16:14 ` Julia Lawall
2023-03-12 15:56 ` Khadija Kamran
2023-03-12 16:15 ` Julia Lawall
2023-03-12 17:16 ` Deepak R Varma
2023-03-12 17:31 ` Sumitra Sharma
2023-03-12 17:46 ` Khadija Kamran
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=20230312152701.GA28100@ubuntu \
--to=sumitraartsy@gmail.com \
--cc=julia.lawall@inria.fr \
--cc=outreachy@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.