public inbox for gentoo-soc@lists.gentoo.org
 help / color / mirror / Atom feed
From: Denis Romanchuk <den4ikkss@gmail.com>
To: gentoo-soc@lists.gentoo.org, radhermit@gentoo.org
Subject: [gentoo-soc] Re: libebuild - weekly report #10
Date: Mon, 01 Aug 2016 01:58:57 +0300	[thread overview]
Message-ID: <2176422.zCvBQJz7fe@yo> (raw)
In-Reply-To: <63863448.Y69znmlREn@yo>

Hello,

My tenth week progress:
Making a couple of pkgcore bugfix and enhancement related PRs
https://github.com/pkgcore/pkgcore/pulls

My plan for the next week:
Pick some new issues from pkgcore list, finish opened PRs considering related 
discussions and reviews. In particular, complete restriction related PR which 
may trigger more refactoring/improvement of restriction module. Think about 
what other modules might be added to libebuild.

Libebuild repo https://github.com/den4ix/libebuild
Libebuild blog https://blogs.gentoo.org/gsoc2016-libebuild/

--
Denis Romanchuk
Kiev, Ukraine
Email: den4ikkss@gmail.com


      reply	other threads:[~2016-07-31 23:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-29 20:55 [gentoo-soc] libebuild - weekly report #1 Denis Romanchuk
     [not found] ` <20160529210437.GA15760@tarragon.radhermit.com>
     [not found]   ` <3632285.5djuBY1Kdt@yo>
2016-06-06  0:37     ` [gentoo-soc] libebuild - weekly report #2 Denis Romanchuk
2016-06-13  3:42       ` [gentoo-soc] Re: libebuild - weekly report #3 Denis Romanchuk
2016-06-20  4:36         ` [gentoo-soc] Re: libebuild - weekly report #4 Denis Romanchuk
2016-06-26 23:14           ` [gentoo-soc] Re: libebuild - weekly report #5 Denis Romanchuk
2016-07-11  2:01             ` [gentoo-soc] Re: libebuild - weekly report #7 Denis Romanchuk
2016-07-18  3:50               ` [gentoo-soc] Re: libebuild - weekly report #8 Denis Romanchuk
2016-07-31 22:58                 ` Denis Romanchuk [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=2176422.zCvBQJz7fe@yo \
    --to=den4ikkss@gmail.com \
    --cc=gentoo-soc@lists.gentoo.org \
    --cc=radhermit@gentoo.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