All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daiane Angolini" <daiane.angolini@foundries.io>
To: meta-freescale@lists.yoctoproject.org
Subject: Re: Issues on github.com/Freescale projects
Date: Wed, 18 Aug 2021 13:02:37 -0300	[thread overview]
Message-ID: <CA+HEL781P+hNfcMtfBBMf3cQdmhBFZKaXLWnwBwG+mmn7OG89w@mail.gmail.com> (raw)
In-Reply-To: <CA+HEL792b8Bc_xRGptKHJxn5ouit-RWhjM1q1EzMVDkbM935zg@mail.gmail.com>

On Sun, Aug 15, 2021 at 12:34 PM Daiane Angolini
<daiane.angolini@foundries.io> wrote:
>
> Hi everyone,
>
> I see a lot of open issues from the past 2 or 3 years on
> github/Freescale projects and I'm trying to (slowly) address them as
> best I can.
>
I am finally reviewing 2020 (latest updated) issues. My plan is to
close as much as possible, and to clean what is still an issue and
what was already solved by the normal development.

It is unfortunate that we don't actually had/have time to reply to all
of them, but I got the impression that a lot was replied at time, and
only a few issues were sitting there waiting for the future to happen.

Anyway, my point is to decrease the open issue list, so we can try to
better focus. If anyone has a better idea on how to deal with it,
please let me know.

BR,
Daiane

> I'm going to close some of them, and try to assign them when I think
> it's an "easy" answer, but I am sure I will make mistakes and I
> apologize in advance, so I'm counting on the authors to help guide me
> during this process.
>
> If you have any suggestions, please let me know.
>
> Daiane

  parent reply	other threads:[~2021-08-18 16:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-15 15:34 Issues on github.com/Freescale projects Daiane Angolini
2021-08-15 20:24 ` [meta-freescale] " Cengiz Can
2021-08-16 13:55   ` Daiane Angolini
2021-08-16 16:02     ` Cengiz Can
2021-08-18 16:02 ` Daiane Angolini [this message]
     [not found] ` <169C720E7FA02E88.9306@lists.yoctoproject.org>
2021-09-21 13:56   ` Daiane Angolini

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=CA+HEL781P+hNfcMtfBBMf3cQdmhBFZKaXLWnwBwG+mmn7OG89w@mail.gmail.com \
    --to=daiane.angolini@foundries.io \
    --cc=meta-freescale@lists.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.