Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Joe MacDonald <Joe.MacDonald@windriver.com>
Cc: yocto@yoctoproject.org,
	openembedded-devel@lists.openembedded.org,
	openembedded-core@lists.openembedded.org
Subject: Re: New OE layer index now available
Date: Mon, 01 Apr 2013 12:57:03 +0100	[thread overview]
Message-ID: <1410613.FPl62IiBfB@helios> (raw)
In-Reply-To: <20130401104758.GB9978@windriver.com>

On Monday 01 April 2013 06:47:59 Joe MacDonald wrote:
> I like it, though I have a couple of questions about the accounts
> themselves.
> 
>    - Any chance we could have them connected (or use the same
>      credentials as) the patchworks ones?

Seems like they are both based on Django so I guess it would be possible; the 
only impediment (assuming there was no Django version mismatch) would be that 
patchwork is currently on different infrastructure.

>    - If not, what options can we set on accounts?  Right now I just see
>      "log out" and "change password".  Both pretty important, but I'd
>      also like to add alternate email addresses, for example, since I
>      use two quite regularly and update meta-networking from both.

There's no alternate email address field; one could be added I suppose but the 
question is, how would you like this to be used within the index?

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



  parent reply	other threads:[~2013-04-01 12:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-29 21:34 New OE layer index now available Paul Eggleton
2013-03-29 21:58 ` Otavio Salvador
2013-03-29 22:07   ` Paul Eggleton
     [not found] ` <20130401104758.GB9978@windriver.com>
2013-04-01 11:57   ` Paul Eggleton [this message]
2013-04-04 15:01 ` Nicolas Dechesne
2013-04-04 15:23   ` Paul Eggleton

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=1410613.FPl62IiBfB@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=Joe.MacDonald@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=yocto@yoctoproject.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