All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Oberritter <obi@opendreambox.org>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: proposal: remove DirectFB from oe-core in the next release cycle
Date: Fri, 22 Jan 2016 19:06:01 +0100	[thread overview]
Message-ID: <56A26F89.8080505@opendreambox.org> (raw)
In-Reply-To: <CAJTo0LaAY=Bru-JzaNMQe5KNuAH3+A0VW_mQ6sNy4GvDU7nk6w@mail.gmail.com>

On 22.01.2016 17:12, Burton, Ross wrote:
> 
> On 22 January 2016 at 15:38, Andreas Oberritter <obi@opendreambox.org
> <mailto:obi@opendreambox.org>> wrote:
> 
>     FWIW, https://github.com/deniskropp/DirectFB is the new location of the
>     upstream repository. I see that you opened an issue there, so you're
>     already aware. The last commit is from October 2015.
> 
> 
> I guess the thing missing is an indication that the repo on github is
> official and maintained.  Specifically the deniskropp repo has been
> recently touched but you have to admit
> that https://github.com/DirectFB/directfb looks more official.

Denis Oliver Kropp is the main developer of DirectFB and the description
of https://github.com/deniskropp/DirectFB says "Official DirectFB GitHub
Repository".

Regards,
Andreas


  reply	other threads:[~2016-01-22 18:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-22 12:58 proposal: remove DirectFB from oe-core in the next release cycle Alexander Kanavin
2016-01-22 13:04 ` Otavio Salvador
2016-01-22 15:38 ` Andreas Oberritter
2016-01-22 16:12   ` Burton, Ross
2016-01-22 18:06     ` Andreas Oberritter [this message]
2016-01-22 18:12       ` Burton, Ross
2016-01-22 19:10       ` alexander.kanavin
2016-01-22 18:49         ` Khem Raj
2016-02-01 10:21           ` Burton, Ross
2016-02-01 19:13             ` Andre McCurdy
2016-02-01 20:54               ` Burton, Ross
2016-01-22 18:47 ` Khem Raj

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=56A26F89.8080505@opendreambox.org \
    --to=obi@opendreambox.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.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 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.