xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Igor Kozhukhov <ikozhukhov@gmail.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "Egger, Christoph" <chegger@amazon.de>,
	Ian Jackson <ian.jackson@eu.citrix.com>,
	xen-devel@lists.xen.org
Subject: Re: [PATCH 1 of 1] Update ZFS sources from illumos.org:
Date: Mon, 11 Nov 2013 21:31:06 +0400	[thread overview]
Message-ID: <BC99198F-2DA4-4522-BF38-695F5B5C8F33@gmail.com> (raw)
In-Reply-To: <1384190609.1883.6.camel@kazak.uk.xensource.com>



On Nov 11, 2013, at 9:23 PM, Ian Campbell wrote:

> 
> On Mon, 2013-11-11 at 21:16 +0400, Igor Kozhukhov wrote:
>> Hi Ian,
>> 
>> we can use:
>> https://github.com/illumos/illumos-gate/tree/master/usr/src/grub@2acef22db7808606888f8f92715629ff3ba555b9
>> 
>> will it be correct ?
>> change set after '@'
> 
> That link is 404 for me.
> 
Could you please let me know how to get URL+changes et on GITHUB or another version control system ?
my URL contain:
main URL: https://github.com/illumos/illumos-gate/tree/master/usr/src/grub
changeset: 2acef22db7808606888f8f92715629ff3ba555b9

for compare with next updates if needed.


>> about -Werror
>> 
>> by GCC specific, if we want to disable some warnings we should add rules after -Werror.
>> example:
>> -Werror -Wno-parentheses -Wno-unused
>> 
>> if we add rules "-Wno-parentheses -Wno-unused" before "-Werror" - they will be ignored and we will have build problem.
> 
> Are you sure? We have at least some instances of this in our tree
> already and it doesn't seem to be having any adverse impact.
> 
> The Werror docs don't say anything about this requirement, just "Make
> all warnings into errors.". Since Werror doesn't actually enable or
> disable any warnings itself I can't see why the ordering would matter.
> 
Yes - i'm sure. I have tested my changes with my rules before "-Werror" - they was ignored and i can see build issues. I have tested by gcc44 and gcc47.

> Ian.
> 

-Igor

  parent reply	other threads:[~2013-11-11 17:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-31 19:04 [PATCH 0 of 1] [PATCH v2] update ZFS for pygrub from illumos Igor Kozhkuhov
2013-10-31 19:04 ` [PATCH 1 of 1] Update ZFS sources from illumos.org: Igor Kozhkuhov
2013-11-11 16:23   ` Ian Campbell
2013-11-11 16:38     ` Egger, Christoph
2013-11-11 16:40       ` Ian Campbell
2013-11-11 16:57         ` Igor Kozhukhov
2013-11-11 17:16           ` Igor Kozhukhov
2013-11-11 17:23             ` Ian Campbell
2013-11-11 17:31               ` Igor Kozhukhov
2013-11-11 17:31               ` Igor Kozhukhov [this message]
2013-11-11 17:34                 ` Ian Campbell
2013-11-11 17:47                   ` Igor Kozhukhov
2013-11-11 16:57     ` Igor Kozhukhov
2013-11-11 17:05       ` Ian Campbell

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=BC99198F-2DA4-4522-BF38-695F5B5C8F33@gmail.com \
    --to=ikozhukhov@gmail.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=chegger@amazon.de \
    --cc=ian.jackson@eu.citrix.com \
    --cc=xen-devel@lists.xen.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;
as well as URLs for NNTP newsgroup(s).