From: Nathan Cutler <ncutler@suse.cz>
To: Loic Dachary <loic@dachary.org>, ceph-devel@vger.kernel.org
Subject: Re: Backporting from Infernalis and c++11
Date: Tue, 15 Sep 2015 10:11:39 +0200 [thread overview]
Message-ID: <55F7D2BB.2050403@suse.cz> (raw)
In-Reply-To: <55F7C70B.4000308@dachary.org>
> With Infernalis Ceph move to c++11 (and CMake), we will see more conflicts when backporting bug fixes to Hammer.
Good point, Loic!
> Any ideas you may have to better deal with this would be most welcome.
A couple thoughts pop into mind.
When I joined the project, I was told that doing backports is a good way
to get into the codebase, and after some months I can confirm that this
is true.
Loic has literally bent over backwards to help me along the way, and
thanks to that I have made some progress. Still, the factor determining
whether a backport is trivial or non-trivial is often my own
"cluenessness".
I would suggest to developers that they keep backporting in the back of
their mind as they design and implement bugfixes. Will the backport be
doable even by a relatively inexperienced backporter? Is there a way to
make it easier on the backporter?
I would suggest that it is in the developers' best interest to make a
little extra effort in this direction, as it will reduce the
probability of the backporter asking them for help later ;-)
Regards
--
Nathan Cutler
Software Engineer Distributed Storage
SUSE LINUX, s.r.o.
Tel.: +420 284 084 037
next prev parent reply other threads:[~2015-09-15 8:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-15 7:21 Backporting from Infernalis and c++11 Loic Dachary
2015-09-15 8:11 ` Nathan Cutler [this message]
2015-09-15 10:02 ` John Spray
2015-09-15 10:19 ` Loic Dachary
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=55F7D2BB.2050403@suse.cz \
--to=ncutler@suse.cz \
--cc=ceph-devel@vger.kernel.org \
--cc=loic@dachary.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.