All of lore.kernel.org
 help / color / mirror / Atom feed
From: tolga.ceylan@gmail.com (Tolga Ceylan)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Fwd: Eudyptula challenge submissions (patch versus proof)
Date: Mon, 2 Feb 2015 12:03:38 -0800	[thread overview]
Message-ID: <CALmu+Sy-sPPJ3nKN2_OGhydYK8tud+eb3YO1OUxqChzPDhdWhw@mail.gmail.com> (raw)
In-Reply-To: <CALmu+SzdND-xLabBuVrR48U=wX-7K4TdOmstNQMVKHRZWr5ifQ@mail.gmail.com>

I think due to my e-mail below, I was removed from the challenge.

Or maybe it was due to the way I submitted the task; separate e-mail
for proof and another kernel patch e-mail...

I'm not sure if this is due to some script parsing some keywords in
kernelnewbies list, but let this be a warning for the rest of you
who are taking this challenge...

I find this unnecessarily harsh especially when the system
takes a very long time to process e-mails and when there's
no outlet for process related questions such as mine below.

All I wanted to find out was if proof should be in the patch
itself or if it's OK to send separate e-mails.

It really should be OK to ask for help for harmless submission related
questions such as how to use thunderbird or git send-email.

Cheers,
Tolga


---------- Forwarded message ----------
From: Tolga Ceylan <tolga.ceylan@gmail.com>
Date: Mon, Feb 2, 2015 at 11:23 AM
Subject: Eudyptula challenge submissions (patch versus proof)
To: kernelnewbies <kernelnewbies@kernelnewbies.org>


Quick question about how to submit patches and proofs. Are separate
emails OK with this? For example;

1) a "formal" kernel patch submitted via git send-email
2) proof e-mail submitted via replying to the original task email

Or should the proof be in the git commit description itself?

Cheers,
Tolga

  reply	other threads:[~2015-02-02 20:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-02 19:23 Eudyptula challenge submissions (patch versus proof) Tolga Ceylan
2015-02-02 20:03 ` Tolga Ceylan [this message]
2015-02-03 16:10   ` Fwd: " Jerry Snitselaar
2015-02-04  4:20     ` sanjeev sharma

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=CALmu+Sy-sPPJ3nKN2_OGhydYK8tud+eb3YO1OUxqChzPDhdWhw@mail.gmail.com \
    --to=tolga.ceylan@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.org \
    /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.