maria-developers team mailing list archive
-
maria-developers team
-
Mailing list archive
-
Message #05214
Re: Determining to which project a patch should be sent.
Hi Sergei,
Thanks, I'll do that.
- Christian
On Wed, Feb 20, 2013 at 2:50 AM, Sergei Golubchik <serg@xxxxxxxxxxxx> wrote:
> Hi, Christian!
>
> On Feb 19, Christian Convey wrote:
>> Hi guys,
>>
>> As I work through the Coverity Scan results of MariaDB's trunk, I find
>> myself having to research what some functions do, and the meanings of
>> their parameters and return values. Rather than just recording what I
>> learn on a piece of paper, I thought it might be nice to write Doxygen
>> comments for some of those functions / structs / etc. That way,
>> perhaps other persons trying to learn the code base could benefit.
>>
>> Here's the problem. Based on Monty's blog posting about MariaDB 10
>> vs. MySQL 5.6 ( http://blog.mariadb.org/mariadb-10-0-and-mysql-5-6/ ),
>> it's not obvious to me which files / functions / etc. in MariaDB have
>> been forked from MariaDB, vs. which ones will be replaced with the
>> corresponding MySQL code when the next MySQL release comes out. This
>> means that when I write Doxygen comments for a given file / function
>> /struct / etc., I don't know whether to submit that comment patch to
>> the MariaDB project or to the MySQL project.
>>
>> Does anyone know I I can figure that out?
>
> Are you looking at 10.0?
> Feel free to send everything to us.
>
> Regards,
> Sergei
References