All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: akuster <akuster@mvista.com>
Cc: yocto@yoctoproject.org
Subject: Re: [PATCH 00/10] Misc fixes (cover letter only)
Date: Thu, 07 Feb 2019 11:57:19 +1300	[thread overview]
Message-ID: <9627074.qSn1cPC3sq@localhost.localdomain> (raw)
In-Reply-To: <788e482f-5fd3-b3ce-4be4-943bbd47ae27@mvista.com>

Oops, yes, I forgot the [layerindex-web], my apologies.

I can cc the oe-devel list if people really want to see it there as well; up 
to this point we've been using this list only. The other option would be a 
dedicated list but I suspect that would have a very limited subscription.

Cheers,
Paul

On Thursday, 7 February 2019 11:24:24 AM NZDT akuster wrote:
> 
> Hello Paul.
> 
> On 2/6/19 2:00 PM, Paul Eggleton wrote:
> > The following changes since commit 
61e9b048591adab88d1996646286e1d7df024bea:
> >
> >   Fix drop-down alignment on duplicates page (2018-11-20 11:58:42 +1300)
> >
> > are available in the Git repository at:
> >
> >   git://git.yoctoproject.org/layerindex-web paule/fixes12
> >   http://git.yoctoproject.org/cgit.cgi/layerindex-web/log/?h=paule/fixes12
> >
> > Paul Eggleton (10):
> >   Send people an email when another user adds them as a maintainer
> >   Add links to other branch recipes in recipe detail
> >   Fix errors due to races deleting bitbake temp files
> >   local.conf: allow for upstream_tracking.inc to be missing
> >   Use try...finally or with to ensure files get closed
> >   Replace use of assert with exceptions
> >   docker: add wget to dependencies
> >   RRS: fix sorting arrow positioning
> >   rrs_maintainer_history: check out layer branch before looking for
> >     maintainers.inc
> >   RRS: add tool to import/export upstream history data
> 
> Thanks for the updates and fixes. This is  a very useful tool to both YP
> and OE. 
> 
> I had to look at what was actual changes to figure out what this patch
> set was against.  Should we change the "subject" to help clarify? ie
> [layer-index][PATCH ...?
> 
> The layer index is hosted on OE. Should one of the  OE mailing be CC'ed??
> 
> Yes I realize the sources are hosted on YP but the url for the tool is
> http://layers.openembedded.org. can be confusing.
> 
> kind regards,
> Armin
> >
> >  Dockerfile                                 |   1 +
> >  conf/local.conf                            |   2 +-
> >  layerindex/bulkchange.py                   |  18 +-
> >  layerindex/update.py                       |   4 +-
> >  layerindex/update_layer.py                 |  14 +-
> >  layerindex/utils.py                        |  21 ++-
> >  layerindex/views.py                        |  70 ++++++--
> >  rrs/tools/historytool.py                   | 196 +++++++++++++++++++++
> >  rrs/tools/rrs_distros.py                   |  19 +-
> >  rrs/tools/rrs_maintainer_history.py        |  45 ++---
> >  rrs/tools/rrs_upgrade_history.py           |   4 +-
> >  rrs/tools/rrs_upstream_history.py          |   3 +-
> >  rrs/tools/upgrade_history_internal.py      |   3 +-
> >  rrs/views.py                               |   2 +
> >  templates/layerindex/maintemail.txt        |   9 +
> >  templates/layerindex/maintemailsubject.txt |   1 +
> >  templates/layerindex/recipedetail.html     |  27 +++
> >  templates/rrs/maintainers.html             |   2 +-
> >  templates/rrs/recipedetail.html            |  27 +++
> >  templates/rrs/recipes.html                 |   2 +-
> >  20 files changed, 392 insertions(+), 78 deletions(-)
> >  create mode 100755 rrs/tools/historytool.py
> >  create mode 100644 templates/layerindex/maintemail.txt
> >  create mode 100644 templates/layerindex/maintemailsubject.txt
> >
> 
> 


-- 

Paul Eggleton
Intel Open Source Technology Centre




      reply	other threads:[~2019-02-06 22:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-06 22:00 [PATCH 00/10] Misc fixes (cover letter only) Paul Eggleton
2019-02-06 22:24 ` akuster
2019-02-06 22:57   ` Paul Eggleton [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=9627074.qSn1cPC3sq@localhost.localdomain \
    --to=paul.eggleton@linux.intel.com \
    --cc=akuster@mvista.com \
    --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 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.