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