All of lore.kernel.org
 help / color / mirror / Atom feed
From: etsai042@gmail.com
To: outreachy-kernel <outreachy-kernel@googlegroups.com>
Subject: Re: [Outreachy kernel] Re: [PATCH v4 0/4] Correct malformed SPDX-License-Identifier
Date: Tue, 12 Mar 2019 02:17:14 -0700 (PDT)	[thread overview]
Message-ID: <f78f67de-a830-4a12-a138-b58ad2954cb0@googlegroups.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1903120946590.2728@hadrien>


[-- Attachment #1.1: Type: text/plain, Size: 1498 bytes --]



On Tuesday, March 12, 2019 at 1:47:32 AM UTC-7, Julia Lawall wrote:
>
>
>
> On Tue, 12 Mar 2019, etsa...@gmail.com <javascript:> wrote: 
>
> > Thanks greg! I'll be more careful with this next time! 
>
> Don't top post.  You should put your reply under the text you are replying 
> to, as I have done here. 
>
> julia 
>
>
Sorry to top post again :( I definitely won't do this.

Wentao
 

> > Wentao  
> > 
> > On Saturday, March 9, 2019 at 2:12:36 AM UTC-8, gregkh wrote: 
> >       >That's 4 patches, which is great, but you sent out 5 patches in 
> >       this 
> >       >series :( 
> >       > 
> >       >Odds are you had a file that ended in .patch in the directory 
> >       when you 
> >       >sent this out.  It happens to everyone :) 
> >       > 
> >       >I'll just drop it and focus on the numbered patches. 
> >       > 
> >       >thanks, 
> >       > 
> >       >greg k-h 
> > 
>
 

> > -- 
> > You received this message because you are subscribed to the Google 
> Groups 
> > "outreachy-kernel" group. 
> > To unsubscribe from this group and stop receiving emails from it, send 
> an 
> > email to outreachy-kern...@googlegroups.com <javascript:>. 
> > To post to this group, send email to outreach...@googlegroups.com 
> <javascript:>. 
> > To view this discussion on the web visithttps://
> groups.google.com/d/msgid/outreachy-kernel/43cdfcbb-f6de-4a92-aa99- 
> > 14bf6e7b228c%40googlegroups.com. 
> > For more options, visit https://groups.google.com/d/optout. 
> > 
> >


[-- Attachment #1.2: Type: text/html, Size: 3875 bytes --]

      reply	other threads:[~2019-03-12  9:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-09  7:31 [PATCH v4 0/4] Correct malformed SPDX-License-Identifier Wentao Cai
2019-03-09  7:31 ` [PATCH v4 1/4] Staging: most: dim2: errors.h: Correct SPDX-License-Identifier Wentao Cai
2019-03-09  7:31 ` [PATCH] Staging: most: dim2: Fix SPDX-License-Identifier in reg.h Wentao Cai
2019-03-09  7:31 ` [PATCH v4 2/4] Staging: most: dim2: hal.h: Correct SPDX-License-Identifier Wentao Cai
2019-03-09  7:31 ` [PATCH v4 3/4] Staging: most: dim2: sysfs.h: " Wentao Cai
2019-03-09  7:31 ` [PATCH v4 4/4] Staging: most: dim2: reg.h: " Wentao Cai
2019-03-09 10:12 ` [PATCH v4 0/4] Correct malformed SPDX-License-Identifier Greg KH
2019-03-12  8:42   ` etsai042
2019-03-12  8:47     ` [Outreachy kernel] " Julia Lawall
2019-03-12  9:17       ` etsai042 [this message]

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=f78f67de-a830-4a12-a138-b58ad2954cb0@googlegroups.com \
    --to=etsai042@gmail.com \
    --cc=outreachy-kernel@googlegroups.com \
    /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.