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
Great to know!!!
On Feb 14, 2011, at 2:28 PM, Emmanuel Bernard wrote:
> Here is the method I've just used.
> I work on say 3.6 and apply n commits, ideally I do apply my changes so that
> each commit does not cross several modules (ie core and entitymanager)
>
> For each commit:
> cd targeted-m
Here is the method I've just used.
I work on say 3.6 and apply n commits, ideally I do apply my changes so that
each commit does not cross several modules (ie core and entitymanager)
For each commit:
cd targeted-module
git diff --no-prefix previous-commit-sha1 actual-commit-sha1 | patch -p1
The
