File: README.maintainer

package info (click to toggle)
libdfp 1.0.17-0.1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 16,172 kB
  • sloc: ansic: 255,724; sh: 4,225; makefile: 703; awk: 461; python: 432; cpp: 254
file content (64 lines) | stat: -rw-r--r-- 1,962 bytes parent folder | download | duplicates (5)
1
2
3
4
5
6
7
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
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
===========================================================================

				    Libdfp
	  The "Decimal Floating Point C Library" Maintainer's Guide
		     for the GNU/Linux OS and GLIBC 2.10+
			Contributed by IBM Corporation
		 Copyright (C) 2011-2014 Free Software Foundation

===========================================================================
NOTE:Eight space tabs are the optimum editor setting for reading this file.
===========================================================================

		 Author(s) : Ryan S. Arnold <rsa@us.ibm.com>
			Date Created: February 9, 2011

---------------------------------------------------------------------------
Table of Contents:

	1.  Introduction
	2.  Libdfp API Changes
	3.  Libdfp ABI Changes
	4.  Versioning
	5.  Contributing

---------------------------------------------------------------------------
2.  Libdfp API Changes

When new functions or interfaces are added to Libdfp then the API has changed
and the library version must change.  For guidelines on adding new symbols to
a particular version see README.developer.

---------------------------------------------------------------------------
3.  Libdfp API Changes

TODO

---------------------------------------------------------------------------
4.  Versioning

TODO

---------------------------------------------------------------------------
5.  Contributing

Libdfp is developed now using GIT SCM at github.  Main site is:

	https://github.com/libdfp/libdfp

General developement follows the simple guideline:

	1. Make sure you have a GitHub account

	2. Fork the repository to your account.

	3. Make the changes and run the testcases. We only take pull requests
	   with passing tests.

	4. If it is applicable, improve or add the current testcases to cover
	   for the new functionality.

	5. Libdfp also uses the ChangeLog with the same format and rules as
	   the GLIBC one.

	6. Push to your fork and submit a pull request.