public inbox for gentoo-soc@lists.gentoo.org
 help / color / mirror / Atom feed
From: listout <brahmajit.xyz@gmail.com>
To: gentoo-soc <gentoo-soc@lists.gentoo.org>
Subject: [gentoo-soc] Week 9 report on porting Gentoo packages to modern C
Date: Sun, 30 Jul 2023 23:55:15 +0530	[thread overview]
Message-ID: <uuwyfhjpx4yarppo3qs6gn3xbexuqrsdjbj34yxirjkgey2yya@qiktcogcpw3c> (raw)

[-- Attachment #1: Type: text/plain, Size: 1266 bytes --]

Hello all, hope you're doing well. This is my week 9 report for my
project "Porting Gentoo's packages to modern C"

Current:
Similar to last week, I picked up bugs at random and started submitting
patches. But this time I made sure to check out the upstream and send in
patches whenever possible, if it turned out to be difficult or I
couldn't find upstream I made sure to make a note about it in the PR
either via commit message or through a separate comment. This way it'll
help my Sam keep track of things and my progress.

Apart from that nothing new or interesting unfortunately.

Next:
Coming next week the plan is the same, pick up more bugs and send in
PRs, both in ::gentoo and upstream whenever possible. I also have some
free time coming week, so plan to make up for lost time during my sick
days in the coming week, as there still lots of packages that require
patching.

I would like to note here, that I made an extra blog post last week
about setting testing environment using lxc and the knowledge about
using gentoo's stage-3 tarballs to create custom lxc gentoo images. I
don't really expect anyone following it or using it, mainly put that up
for future reference for myself.

Till then, see ya!
-- 
Regards,
listout

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

                 reply	other threads:[~2023-07-30 18:25 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=uuwyfhjpx4yarppo3qs6gn3xbexuqrsdjbj34yxirjkgey2yya@qiktcogcpw3c \
    --to=brahmajit.xyz@gmail.com \
    --cc=gentoo-soc@lists.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