DESCRIPTION

Add xxx@xxx.xxx 3.0 tags

Change-Id: Iad4dcb0ed26c60a947d8ba65b7afe26efd00b481
Signed-off-by: Sebastian Porter xxx@xxx.xxx


COMMENTS

author: Sebastian Porter
date: 2013-04-16 14:35:17.000000000

Patch Set 1: Verified; Looks good to me, approved; IP review completed

Submitting trivial change.

-------------------------------------
author: Sebastian Porter
date: 2013-04-16 14:35:18.000000000

Change has been successfully merged into the git repository.

-------------------------------------
author: Juliet Cantu
date: 2013-04-16 21:20:27.000000000

Patch Set 1: (1 inline comment)



Line:153, org.eclipse.egit.core/src/org/eclipse/egit/core/CoreText.java -> The whole class should be made internal instead

-------------------------------------
author: Sebastian Porter
date: 2013-04-17 07:18:47.000000000

Patch Set 1:

> The whole class should be made internal instead

If EGit follows the general Eclipse API rules [1], then this would be a breaking API change.

[1] http://www.eclipse.org/articles/Article-API-Use/index.html

-------------------------------------
author: Juliet Cantu
date: 2013-04-17 18:51:53.000000000

Patch Set 1:

Yes, and this is a new Major version.

-------------------------------------
author: Sebastian Porter
date: 2013-04-18 08:44:01.000000000

Patch Set 1:

> Yes, and this is a new Major version

One should still not break clients if not needed. Though I agree, that those message constants are probably not (widely) used by clients.

-------------------------------------
