MySQL++

Check-in [8b0728e18d]
Login

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Added info on the GitHub mirror to HACKERS.md.
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA3-256: 8b0728e18d8be6e224ed99437a6cb6e33913f764d9b74f584eaff609032e4063
User & Date: tangent 2019-04-22 18:50:22
Context
2019-04-22
19:38
Converted top-level README.txt file to Markdown so it formats more nicely on GitHub and in the Fossil /file view. check-in: d080820431 user: tangent tags: trunk
18:50
Added info on the GitHub mirror to HACKERS.md. check-in: 8b0728e18d user: tangent tags: trunk
18:44
Assorted improvements to the HACKERS.md file check-in: 3aef3560ea user: tangent tags: trunk
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Changes to HACKERS.md.

329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
...
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366










367

368
369
370
371
372
373
374

If you wish to submit a patch to the library, it’s probably simplest to
paste it into a [forum post][for] if it’s small. If it’s large, put it
in Pastebin or similar, then link to it from a forum post.  We want
patches in unified diff format.

We will also accept trivial patches not needing discussion as text
in a Fossil ticket.

The easiest way to get a unified diff is to check out a copy of the
current MySQL++ tree as described above. Then make your change, `cd`
to the MySQL++ root directory, and ask Fossil to generate the patch
for you:

    $ fossil diff > mychange.patch
................................................................................
local branch](#private), then send a [bundle][fb] instead of a patch.

If you've sent patches to MySQL++ before and don't have a Fossil
developer login, another alternative is to ask for a login before you
begin work so that your changes are automatically sync'd to the main
Fossil repository as you work, so you don't have to send bundles or
patch files. We generally don't refuse such requests if you've already
proven your ability to work well with the MySQL++ project.

If you're making a patch against a MySQL++ distribution tarball, then
you can generate a patch this way:

    $ diff -ruN mysql++-olddir mysql++-newdir > mychange.patch

The `diff` command is part of every Unix and Linux system, and should be
installed by default. If you're on a Windows machine, GNU diff is part
of [Cygwin](http://cygwin.com/). Fossil is also available for all of
these systems. There are no excuses for not being able to make unified
diffs. :)











[fb]:  http://fossil-scm.org/fossil/help?cmd=bundle



## The MySQL++ Code Style

Every code base should have a common code style. Love it or
hate it, here are MySQL++'s current code style rules:








|







 







|












>
>
>
>
>
>
>
>
>
>

>







329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
...
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385

If you wish to submit a patch to the library, it’s probably simplest to
paste it into a [forum post][for] if it’s small. If it’s large, put it
in Pastebin or similar, then link to it from a forum post.  We want
patches in unified diff format.

We will also accept trivial patches not needing discussion as text
or attachments to [a Fossil ticket][tkt].

The easiest way to get a unified diff is to check out a copy of the
current MySQL++ tree as described above. Then make your change, `cd`
to the MySQL++ root directory, and ask Fossil to generate the patch
for you:

    $ fossil diff > mychange.patch
................................................................................
local branch](#private), then send a [bundle][fb] instead of a patch.

If you've sent patches to MySQL++ before and don't have a Fossil
developer login, another alternative is to ask for a login before you
begin work so that your changes are automatically sync'd to the main
Fossil repository as you work, so you don't have to send bundles or
patch files. We generally don't refuse such requests if you've already
proven your ability to work productively with the MySQL++ project.

If you're making a patch against a MySQL++ distribution tarball, then
you can generate a patch this way:

    $ diff -ruN mysql++-olddir mysql++-newdir > mychange.patch

The `diff` command is part of every Unix and Linux system, and should be
installed by default. If you're on a Windows machine, GNU diff is part
of [Cygwin](http://cygwin.com/). Fossil is also available for all of
these systems. There are no excuses for not being able to make unified
diffs. :)

Although MySQL++ does have a [GitHub mirror][ghm], we do not acccept PRs
via that channel, because the mirror is read-only. You can still send us
a PR through GitHub, but realize that what’s going to happen on the back
end is that we’ll generate a patch and apply it to the Fossil repo by
hand, then update the mirror, so you won’t get GitHub credit for the PR.
Sorry; there’s no easy way for this mirroring system to accept
contributions back the other direction. If you want credit for the
commit, ask us for an account on the Fossil repo and commit it there
instead.

[fb]:  http://fossil-scm.org/fossil/help?cmd=bundle
[tkt]: https://tangentsoft.com/mysqlpp/tktnew


## The MySQL++ Code Style

Every code base should have a common code style. Love it or
hate it, here are MySQL++'s current code style rules: