commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Gregory <>
Subject Re: [VFS] code comment cleanups (GitHub Pull#1)
Date Sat, 28 Sep 2013 17:01:28 GMT
Hello Bernd,

I am sorry for the delay in replying to you.

The best input to any Commons project is to create a Jira and attach a
patch in diff file format.

As for our process, Github is fun but we only use it as a mirror and it
just makes it harder to merge changes back in SVN. So I am not sure why we
do that in the first place instead of switching the project to Git, but
that's a different story.


On Wed, Sep 25, 2013 at 7:57 PM, Bernd Eckenfels <>wrote:

> Hello,
> I rebased Pull#1 against trunk and made a fixup of the commits into one.
> Do I need to file it on Jira?
> Greetings
> Bernd
> Am 18.09.2013, 22:00 Uhr, schrieb Bernd Eckenfels <
> >:
>  all over the VFS core and providers there are many places where code is
>> commented out. Most of the time it looks like it is old code, but sometimes
>> it also looks like suggested new implementations or even TODO style of
>> things.
>> I started to remove some of the places, especially where it looks obvious
>> to me that it is simply commented out code variantes of older versions.
>> Also some other minor comment related stuff is in this pull request here:
>> Can you check out and see if you think I removed too much or not enough?
>> I did not reviewed all files systematically it is more like the files I
>> happen to look at anyway.
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: dev-unsubscribe@commons.**<>
> For additional commands, e-mail:

E-Mail: |
Java Persistence with Hibernate, Second Edition<>
JUnit in Action, Second Edition <>
Spring Batch in Action <>

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message