On 09/19/2014 03:40 PM, Richard Shaw wrote:
I guess I could have copied the module into my project module folder and
applied it locally, but that seems like a worse workaround than patching at
the distro level.
I think I would personally prefer that over changing the package for the
whole dist
On 09/19/2014 03:19 PM, Richard Shaw wrote:
I'd like to hear others opinions, but what I've done is once one of my
patches is accepted, as long as it applies cleanly to the current release
(and since all I mess with are modules that's usually the case) then I just
email the Fedora package maintai
Richard Shaw wrote:
On Fri, Sep 19, 2014 at 1:59 AM, Jiri Malak
wrote:
I did a several fixes to CMake related to Open Watcom which were
accepteed
to current development
branch a few month ago.
Up to now they were not included to official version 3.0 branch.
What I must do to be include or I
On Fri, Sep 19, 2014 at 8:34 AM, Nils Gladitz wrote:
> On 09/19/2014 03:19 PM, Richard Shaw wrote:
>
>> I'd like to hear others opinions, but what I've done is once one of my
>> patches is accepted, as long as it applies cleanly to the current release
>> (and since all I mess with are modules tha
On Fri, Sep 19, 2014 at 1:59 AM, Jiri Malak wrote:
> Hi,
>
> I did a several fixes to CMake related to Open Watcom which were accepteed
> to current development
> branch a few month ago.
> Up to now they were not included to official version 3.0 branch.
> What I must do to be include or I doing s
> On 09/19/2014 01:57 PM, Jiri Malak wrote:
>> Thanks for info.
>> It is clear, it was too late to be included to 3.0.
>>
>> Do you have any idea when version 3.1 first release candidate is planned?
>
> Mantis (the issue tracker) currently has 3.1 scheduled for 2014-11-01.
> For now I'd take it as
On 09/19/2014 01:57 PM, Jiri Malak wrote:
Thanks for info.
It is clear, it was too late to be included to 3.0.
Do you have any idea when version 3.1 first release candidate is planned?
Mantis (the issue tracker) currently has 3.1 scheduled for 2014-11-01.
For now I'd take it as a non binding r
> On 09/19/2014 12:40 PM, Jiri Malak wrote:
>> OK, but it was accepted before v3.0.0 was released.
>> Do you know what rules are applied for selection what will be in new release
>> and what cutoff
>> date
>> for it?
>
> On Feb. 19 2014 Brad announced the cutoff [1].
> So everything that was in ma
The "rule" is (roughly): after the first release candidate for a given
release, no more "new features" for that particular release. Only
continuing work to complete new features in rc1 and fixing regressions
reported from previous versions should go in subsequent release
candidates. Possible except
On 09/19/2014 12:40 PM, Jiri Malak wrote:
OK, but it was accepted before v3.0.0 was released.
Do you know what rules are applied for selection what will be in new release
and what cutoff date
for it?
On Feb. 19 2014 Brad announced the cutoff [1].
So everything that was in master before that wi
> On 09/19/2014 08:59 AM, Jiri Malak wrote:
>> I did a several fixes to CMake related to Open Watcom which were accepteed
>> to current development
>> branch a few month ago.
>> Up to now they were not included to official version 3.0 branch. What I must
>> do to be include
or I doing something w
On 09/19/2014 08:59 AM, Jiri Malak wrote:
I did a several fixes to CMake related to Open Watcom which were accepteed to
current development
branch a few month ago.
Up to now they were not included to official version 3.0 branch.
What I must do to be include or I doing something wrong?
The curr
Hi,
I did a several fixes to CMake related to Open Watcom which were accepteed to
current development
branch a few month ago.
Up to now they were not included to official version 3.0 branch.
What I must do to be include or I doing something wrong?
Regards
Jiri
--
Powered by www.kitware.com
13 matches
Mail list logo
