On Wed, Jul 13, 2011 at 10:31 PM, Uwe Schindler <[email protected]> wrote:
> I do exactly the same what Mark described!

+1
>
> -----
> Uwe Schindler
> H.-H.-Meier-Allee 63, D-28213 Bremen
> http://www.thetaphi.de
> eMail: [email protected]
>
>
>> -----Original Message-----
>> From: Mark Miller [mailto:[email protected]]
>> Sent: Wednesday, July 13, 2011 10:20 PM
>> To: [email protected]
>> Subject: Re: svn commit: r1146329 - /lucene/dev/trunk/solr/CHANGES.txt
>>
>> I try to credit the person that raised the bug as well.
>>
>> If someone else raises the bug and I fix it, doing pretty much all of the
> work,
>> then I do "jon doe, mark miller"
>>
>> If someone else raises the bug and does most of the work, and I just have
> to
>> tweak or clean it up a bit at most, I do "jon doe via mark miller"
>>
>> - Mark
>>
>> On Jul 13, 2011, at 4:12 PM, Michael McCandless wrote:
>>
>> > I try to credit whoever raised the bug even if they don't make a
>> > patch, test case, etc.
>> >
>> > The effort to find, characterize, report a bug back to us is sizable
>> > and people should be given credit for that, I think.
>> >
>> > Mike McCandless
>> >
>> > http://blog.mikemccandless.com
>> >
>> > On Wed, Jul 13, 2011 at 4:06 PM, Yonik Seeley
>> > <[email protected]> wrote:
>> >> I think our normal practice has been to include people who have
>> >> actually contributed patches/code or substantial design.
>> >> Not sure if we want to change that practice or not - just relaying
>> >> what has been the norm.
>> >>
>> >> -Yonik
>> >> http://www.lucidimagination.com
>> >>
>> >>
>> >>
>> >> On Wed, Jul 13, 2011 at 3:58 PM,  <[email protected]> wrote:
>> >>> Author: mvg
>> >>> Date: Wed Jul 13 19:58:13 2011
>> >>> New Revision: 1146329
>> >>>
>> >>> URL: http://svn.apache.org/viewvc?rev=1146329&view=rev
>> >>> Log:
>> >>> Added missing entries to CHANGES
>> >>>
>> >>> Modified:
>> >>>    lucene/dev/trunk/solr/CHANGES.txt
>> >>>
>> >>> Modified: lucene/dev/trunk/solr/CHANGES.txt
>> >>> URL:
>> >>>
>> http://svn.apache.org/viewvc/lucene/dev/trunk/solr/CHANGES.txt?rev=1
>> >>> 146329&r1=1146328&r2=1146329&view=diff
>> >>>
>> ==========================================================
>> ==========
>> >>> ==========
>> >>> --- lucene/dev/trunk/solr/CHANGES.txt (original)
>> >>> +++ lucene/dev/trunk/solr/CHANGES.txt Wed Jul 13 19:58:13 2011
>> >>> @@ -365,9 +365,10 @@ Bug Fixes
>> >>>  * SOLR-2623: Solr JMX MBeans do not survive core reloads (Alexey
>> >>> Serba, shalin)
>> >>>
>> >>>  * Fixed grouping bug when start is bigger than rows and format is
>> >>> simple that zero documents are returned even
>> >>> -  if there are documents to display.
>> >>> +  if there are documents to display. (Martijn van Groningen, Nikhil
>> >>> + Chhaochharia)
>> >>>
>> >>> -* SOLR-2564: Fixed ArrayIndexOutOfBoundsException when using
>> simple
>> >>> format and start > 0
>> >>> +* SOLR-2564: Fixed ArrayIndexOutOfBoundsException when using
>> simple
>> >>> +format and
>> >>> +  start > 0 (Martijn van Groningen, Matteo Melli)
>> >>>
>> >>>  * SOLR-2642: Fixed sorting by function when using grouping. (Thomas
>> >>> Heigl, Martijn van Groningen)
>> >>>
>> >>>
>> >>>
>> >>>
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: [email protected] For
>> >> additional commands, e-mail: [email protected]
>> >>
>> >>
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: [email protected] For
>> > additional commands, e-mail: [email protected]
>> >
>>
>> - Mark Miller
>> lucidimagination.com
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected] For additional
>> commands, e-mail: [email protected]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to