From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Brian Avery <avery.brian@gmail.com>
Cc: Christopher Larson <clarson@kergoth.com>,
"bitbake-devel@lists.openembedded.org"
<bitbake-devel@lists.openembedded.org>
Subject: Re: [PATCH 1/1] bitbake: toastergui: Call csrf function in all pages to ensure cookie is sent
Date: Wed, 19 Aug 2015 18:00:48 +0100 [thread overview]
Message-ID: <1440003648.12105.136.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAKV_0egc8fJ5C1VgYC_bD+1kC6_mzwozn5LXgei4UXFoMTGNNw@mail.gmail.com>
On Wed, 2015-08-19 at 07:14 -0700, Brian Avery wrote:
> Noted for the future, sorry. Figured my 1st time would be entertaining :).
>
> Should I resubmit?
Er, I thought we already discussed this and you already did? There is
another version of the patch on the list...
Cheers,
Richard
prev parent reply other threads:[~2015-08-19 17:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-18 22:10 [PATCH 0/1] Call csrf function in all pages to ensure cookie is sent brian avery
2015-08-18 22:11 ` [PATCH 1/1] bitbake: toastergui: " brian avery
2015-08-19 1:41 ` Christopher Larson
2015-08-19 14:14 ` Brian Avery
2015-08-19 17:00 ` Richard Purdie [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=1440003648.12105.136.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=avery.brian@gmail.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=clarson@kergoth.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox