All of lore.kernel.org
 help / color / mirror / Atom feed
From: Loic Dachary <loic@dachary.org>
To: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Backporting from Infernalis and c++11
Date: Tue, 15 Sep 2015 09:21:47 +0200	[thread overview]
Message-ID: <55F7C70B.4000308@dachary.org> (raw)

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

Hi Ceph,

With Infernalis Ceph move to c++11 (and CMake), we will see more conflicts when backporting bug fixes to Hammer. Any ideas you may have to better deal with this would be most welcome. Since these conflicts will be mostly cosmetic, they should not be too difficult to resolve. The trick will be for someone not familiar with the codebase to separate what is cosmetic and what is not.

This does not happen yet, no immediate concern :-) Maybe if we think about that well in advance we'll be in a better position to deal with it later on ?

Cheers

-- 
Loïc Dachary, Artisan Logiciel Libre


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

             reply	other threads:[~2015-09-15  7:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-15  7:21 Loic Dachary [this message]
2015-09-15  8:11 ` Backporting from Infernalis and c++11 Nathan Cutler
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=55F7C70B.4000308@dachary.org \
    --to=loic@dachary.org \
    --cc=ceph-devel@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.