The same rule applies for all projects.
On Feb 19, 2011, at 3:56 PM, Gunnar Morling wrote:
> Hi,
>
> was there already a final decision on this? I guess the same rule (whichever
> it is) applies to HV, right?
>
> Thanks, Gunnar
>
>
> So from now on we not just update the year, but have the
Hi,
was there already a final decision on this? I guess the same rule (whichever
it is) applies to HV, right?
Thanks, Gunnar
>
> So from now on we not just update the year, but have the 200x-2011
> approach?
>
> --Hardy
> ___
> hibernate-dev mailing l
On Mon, 14 Feb 2011 17:11:32 +0100, Emmanuel Bernard
wrote:
>>> It is not OK to blindly replace a copyright header with another one.
>>> One must at least make sure that:
>>> - the original copyright date is not erased
>>
>> Have the policies changed? The least time we had this discussion on
On 14 févr. 2011, at 16:32, Hardy Ferentschik wrote:
> On Mon, 14 Feb 2011 15:13:10 +0100, Emmanuel Bernard
> wrote:
>
>> It is not OK to blindly replace a copyright header with another one.
>> One must at least make sure that:
>> - the original copyright date is not erased
>
> Have the polic
On Mon, 14 Feb 2011 15:13:10 +0100, Emmanuel Bernard
wrote:
> It is not OK to blindly replace a copyright header with another one.
> One must at least make sure that:
> - the original copyright date is not erased
Have the policies changed? The least time we had this discussion on
hibernate-
Guys,
It is not OK to blindly replace a copyright header with another one.
One must at least make sure that:
- the original copyright date is not erased
- copyright holders included in the header are not removed
For the date, if a file was initially created in 2007 and updated this year (or
any