Hello,
might be a more general point, so I move this discussion from the (closed)
Github pull request to dev@:
Am 25.10.2013, 02:33 Uhr, schrieb Gary Gregory <notificati...@github.com>:
I'm sorry I must have missed something. What .error suffix?
I was refering to the points frim VFS-496 which have been unclear to me
and therefore not contained in the patch:
# The resource key vfs.util/missing-capability.error is not used. It might
be removed
# (or at least fix the message, add a trainling dot and change do/does).
#
# vfs.provider/config-unexpected-primitive.error is actually a warning not
an error/exception,
# should the key be renamed?
There are actually more entries which are not error-ids of warnings but
used for logging warnings.
I am sorry when not using SVN, but it is horribly complicated to use, I am
used to Git. I am not sure why the diffs make problem while applying them
but I also noticed Eclipse has some problems even when the "remove prefix"
is set correct. Looks like the problem is related to "virtual maven child
projects".
Greetings
Bernd
For now, it is better to use SVN and the SVN diff file format. Otherwise
I have to tweak Git diff files by hand, which is obviously error prone.
One day, eventually, I am guessing we will move VFS to Git, but it would
be
Git at Apache, not GitHub.
Gary
On Thu, Oct 24, 2013 at 7:46 PM, Bernd <notificati...@github.com> wrote:
Thanks for the merge. What about the .error suffix?
--
http://bernd.eckenfels.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
