From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Patchwork access
Date: Wed, 19 Jun 2013 21:09:56 +0100 [thread overview]
Message-ID: <1371672596.20823.198.camel@ted> (raw)
In-Reply-To: <D76D4BAB-5FE3-4E5E-9417-AFA7E4986724@gmail.com>
On Wed, 2013-06-19 at 09:42 -0700, Khem Raj wrote:
> On Jun 19, 2013, at 4:40 AM, "Burton, Ross" <ross.burton@intel.com> wrote:
>
> > On 19 June 2013 10:09, Paul Eggleton <paul.eggleton@linux.intel.com> wrote:
> >> A few people have been asking for access to patchwork recently, and it seems
> >> like it isn't possible to create an account at the moment. Can we come up with
> >> a plan to solve this?
>
> The patchwork has same issue as wiki w.r.t to spam and phony account creations,
> disabling the register page from active links reduces it tremendously. I will put interactions
> on wiki on how to still use it after register link is not shown. The functionality is still there
> but it can be seen on website.
>
> >
> > It's also sad that the oe-core patchwork isn't really usable as it's
> > not detecting patches that have been merged. Who's the right person
> > to investigate this?
>
> its a heuristic and best effort approach its not totally automatic. e.g. if V2 of a patch is send
> and V1 is still there then it might close V1 if hashes are same. OE-Core patchwork is mainly
> for reference as it was decided for cherry picking patches etc. for local use its not the patch
> management solution for OE-Core as much as it is for other layers in there.
FWIW I'm having a lot of local success with subject line (commit
summary) matching as I have a script which moves emails around IMAP
depending on the subject line being in the git repo. Its just a quick
hacky script though, nothing special...
Cheers,
Richard
prev parent reply other threads:[~2013-06-19 20:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 9:09 Patchwork access Paul Eggleton
2013-06-19 11:40 ` Burton, Ross
2013-06-19 16:42 ` Khem Raj
2013-06-19 20:09 ` 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=1371672596.20823.198.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-devel@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox