From: Jan Tulak <jtulak@redhat.com>
To: linux-xfs <linux-xfs@vger.kernel.org>
Subject: My thesis about mkfs
Date: Mon, 28 Aug 2017 16:39:48 +0200 [thread overview]
Message-ID: <CACj3i71iYMn8+nwUmXUHfR-c2c8XdqfdTsgx5Ohkb2k1FXUd0w@mail.gmail.com> (raw)
Hi guys
This email is about my thesis I did and which I'm sending you in case
you are interested: Refactoring and Verification of the Code of
mkfs.xfs
The refactoring part (intro and summary of chapter 3) can be somehow
interesting if you want to get a small overview of how it feels to
just jump into a project like this without any experience in regular
development of bigger open source projects (bigger than 1-2 man
shows). Other than that, you won't find there much.
The testing part (chapters 5 and 6) shows how CppCheck, Coverity, and
GCC and Clang compares to each other, in various levels of
aggressiveness. Spoiler: Coverity is pretty good and we are doing well
that we use it. :-)
I'm sorry I didn't publish it right after the defence; I wanted to go
through it and make some minor edits, but in the weeks since the
defence, I forgot what they told me, so I decided I will just send it
as it is, with no other delays. :-)
The thesis was defended and I got a master degree, but I still
appreciate any comments. :-)
Download here:
https://github.com/jtulak/thesis-mmm/releases
Cheers,
Jan
PS: Eric, I hope I didn't overlook anything you pointed out in the
proofreading. Thank you once more for that. :-)
next reply other threads:[~2017-08-28 14:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-28 14:39 Jan Tulak [this message]
2017-08-28 17:43 ` My thesis about mkfs Emmanuel Florac
2017-08-29 0:25 ` Darrick J. Wong
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=CACj3i71iYMn8+nwUmXUHfR-c2c8XdqfdTsgx5Ohkb2k1FXUd0w@mail.gmail.com \
--to=jtulak@redhat.com \
--cc=linux-xfs@vger.kernel.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.