Le 2015-09-24 04:16, Ole Ersoy a écrit :
On 09/23/2015 03:09 PM, Luc Maisonobe wrote:
CM is not intended to be a design pattern people should mimic. We are
so bad at this it would be a shame. No one in its right mind would
copy or reuse this stuff. It is for internal use only and we don't
Hi Gilles,
Le 2015-09-23 23:00, Gilles a écrit :
[...]
CM is not intended to be a design pattern people should mimic.
We are so bad at this
The crux is that the project's team is in effect not _interested_
in this. [And I admit that I had not understood it for a long
time (hence the
On 09/24/2015 06:31 AM, luc wrote:
Le 2015-09-24 04:16, Ole Ersoy a écrit :
On 09/23/2015 03:09 PM, Luc Maisonobe wrote:
CM is not intended to be a design pattern people should mimic. We are so bad at
this it would be a shame. No one in its right mind would copy or reuse this
stuff. It is
Hello,
do we have this rule to include the name of a patch contributor into
the commit message? I havent seen that beeing used so far in
commons-vfs, and the commit does contain Antonio's name in the
changes.xml due-to= credits. I think a while back we had the
discussion that not even this is
There is such requirement for attribution that I know of. The changes.xml is
what I see used most consistently and that's not a requirement either from what
I can tell.
With Git, there is a formal way to trace contributions, but I'm not sure if
that's used at the ASF.
Gary
Original
On 9/24/15 8:59 AM, Bernd wrote:
> Hello,
>
> do we have this rule to include the name of a patch contributor into
> the commit message? I havent seen that beeing used so far in
> commons-vfs, and the commit does contain Antonio's name in the
> changes.xml due-to= credits. I think a while back we
Hi Luc,
I gave this some more thought, and I think I may have tapped out to soon, even
though you are absolutely right about what an exception does in terms bubbling
execution to a point where it stops or we handle it.
Suppose we have an Optimizer and an Optimizer observer. The optimizer
On 9/24/15 9:50 AM, Bernd wrote:
> Phil, Is this somewhere codified?
As I said at the end, I don't think this needs to be codified. The
only actual requirement is CLA / software grant coverage for large
contributions. We have agreed several times (should be in the list
archives) not to
On Thu, 24 Sep 2015 08:43:38 -0500, Ole Ersoy wrote:
On 09/24/2015 06:31 AM, luc wrote:
Le 2015-09-24 04:16, Ole Ersoy a écrit :
On 09/23/2015 03:09 PM, Luc Maisonobe wrote:
CM is not intended to be a design pattern people should mimic. We
are so bad at this it would be a shame. No one in its
On 09/24/2015 03:23 PM, Luc Maisonobe wrote:
Le 24/09/2015 21:40, Ole Ersoy a écrit :
Hi Luc,
I gave this some more thought, and I think I may have tapped out to
soon, even though you are absolutely right about what an exception does
in terms bubbling execution to a point where it stops or
On 09/24/2015 04:05 PM, Gilles wrote:
On Thu, 24 Sep 2015 08:43:38 -0500, Ole Ersoy wrote:
On 09/24/2015 06:31 AM, luc wrote:
Le 2015-09-24 04:16, Ole Ersoy a écrit :
On 09/23/2015 03:09 PM, Luc Maisonobe wrote:
CM is not intended to be a design pattern people should mimic. We are so bad
On Thu, 24 Sep 2015 17:02:15 -0500, Ole Ersoy wrote:
On 09/24/2015 03:23 PM, Luc Maisonobe wrote:
Le 24/09/2015 21:40, Ole Ersoy a écrit :
Hi Luc,
I gave this some more thought, and I think I may have tapped out to
soon, even though you are absolutely right about what an exception
does
in
On Thu, 24 Sep 2015 18:01:13 -0500, Ole Ersoy wrote:
On 09/24/2015 04:05 PM, Gilles wrote:
On Thu, 24 Sep 2015 08:43:38 -0500, Ole Ersoy wrote:
On 09/24/2015 06:31 AM, luc wrote:
Le 2015-09-24 04:16, Ole Ersoy a écrit :
On 09/23/2015 03:09 PM, Luc Maisonobe wrote:
CM is not intended to be a
Le 24/09/2015 21:40, Ole Ersoy a écrit :
> Hi Luc,
>
> I gave this some more thought, and I think I may have tapped out to
> soon, even though you are absolutely right about what an exception does
> in terms bubbling execution to a point where it stops or we handle it.
>
> Suppose we have an
Why should the instance throwing the exception hold a field with the
information?
Separation of concerns: optimizer does the computation,
then the exception holds what's needed for a full report of the failure.
I would see what makes sense on on case by case basis. For example if the
Phil, Is this somewhere codified?
2015-09-24 18:47 GMT+02:00 Phil Steitz :
> On 9/24/15 8:59 AM, Bernd wrote:
>> Hello,
>>
>> do we have this rule to include the name of a patch contributor into
>> the commit message? I havent seen that beeing used so far in
>> commons-vfs,
On 09/24/2015 06:01 PM, Gilles wrote:
On Thu, 24 Sep 2015 17:02:15 -0500, Ole Ersoy wrote:
On 09/24/2015 03:23 PM, Luc Maisonobe wrote:
Le 24/09/2015 21:40, Ole Ersoy a écrit :
Hi Luc,
I gave this some more thought, and I think I may have tapped out to
soon, even though you are absolutely
17 matches
Mail list logo