libtabula

Check-in [60f47c604d]
Login

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

Overview
Comment:Updated our HACKERS.md file to be consistent with the newly-Fossilized MySQL++ HACKERS.md file.
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1: 60f47c604de4c605da7077c90d63b74d5fc90973
User & Date: tangent 2017-06-29 02:59:32
Context
2018-10-27
05:58
Added logo check-in: 318e53556b user: tangent tags: trunk
2017-06-29
02:59
Updated our HACKERS.md file to be consistent with the newly-Fossilized MySQL++ HACKERS.md file. check-in: 60f47c604d user: tangent tags: trunk
2016-02-06
10:22
Whitespace fix check-in: fa93a19a0a user: tangent tags: trunk
Changes
Hide Diffs Side-by-Side Diffs Ignore Whitespace Patch

Changes to HACKERS.md.

     8      8   Code Repository Access
     9      9   ----
    10     10   libtabula 4.0 and newer uses the [Fossil][1] [distributed version
    11     11   control system][2].
    12     12   
    13     13   To clone the code repository anonymously, say:
    14     14   
    15         -    $ fossil clone http://libtabula.org/code libtabula.fossil
           15  +    $ fossil clone https://libtabula.org/code libtabula.fossil
    16     16   
    17     17   If you have a developer account on libtabula.org's Fossil instance, just
    18     18   add your username to the URL like so:
    19     19   
    20         -    $ fossil clone http://username@libtabula.org/code libtabula.fossil
           20  +    $ fossil clone https://username@libtabula.org/code libtabula.fossil
    21     21   
    22     22   That will get you a file called `libtabula.fossil` containing the
    23     23   full history of libtabula from just after the MySQL++ 3.2.1 fork.
    24     24   
    25         -(If you need to dig into libtabula's history prior to the fork,
    26         -see the instructions in [the MySQL++ equivalent to this file][3].)
    27         -
    28     25   You can call that clone file anything you like.  Even the `.fossil`
    29     26   extension is just a convention, not a requirement.
    30     27   
    31     28   Then to "open" the repo clone so you can hack on it, say:
    32     29   
    33     30       $ mkdir libtabula
    34     31       $ cd libtabula
................................................................................
    43     40           libtabula/
    44     41               skull/             # Fossil head, get it?   I crack me up.
    45     42               trunk -> skull/    # Alias to match Fossil branch naming
    46     43                   build/         # Build directory for the skull/trunk
    47     44               some-branch/       # Separately-opened working branch
    48     45                   build/         # Build directory for the working branch
    49     46               4.0.0/             # Release branch checkout
    50         -        mysql++/
    51         -            head/              # Gna! MySQL++ svn trunk checkout
    52         -            3.2.1/             # Release tarball unpacked
           47  +        mysqlpp/
           48  +            head/              # MySQL++ Fossil trunk checkout
           49  +            3.2.3/             # Release tarball unpacked
    53     50   
    54     51   Fossil will let you make any modifications you like to your local
    55     52   repository copy.  For those with privileges on the upstream
    56     53   copy, checkins get automatically synced with it by default.
    57     54   (If you prefer Git or Mercurial style two-phase commits, you
    58     55   can say `fossil settings autosync off`.)  If you don't have such
    59     56   permissions, you just modify your local copy, then have to merge