<feed xmlns='http://www.w3.org/2005/Atom'>
<title>coreutils/README-hacking, branch next</title>
<subtitle>Mirror of https://https.git.savannah.gnu.org/git/coreutils.git/
</subtitle>
<id>https://git.shady.money/coreutils/atom?h=next</id>
<link rel='self' href='https://git.shady.money/coreutils/atom?h=next'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/coreutils/'/>
<updated>2009-08-25T07:21:00Z</updated>
<entry>
<title>maint: remove Local Variables: indent-tabs-mode: nil from all sources</title>
<updated>2009-08-25T07:21:00Z</updated>
<author>
<name>Jim Meyering</name>
<email>meyering@redhat.com</email>
</author>
<published>2009-02-27T16:15:43Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/coreutils/commit/?id=e2808a3999233c7186ee349278dbff5a046250db'/>
<id>urn:sha1:e2808a3999233c7186ee349278dbff5a046250db</id>
<content type='text'>
* src/getlimits.c: Likewise.
* src/group-list.c: Likewise.
* src/groups.c: Likewise.
* src/mktemp.c: Likewise.
* src/setuidgid.c: Likewise.
* src/stdbuf.c: Likewise.
* src/timeout.c: Likewise.
* src/truncate.c: Likewise.
* gl/lib/mbsalign.c: Likewise.
* tests/test-lib.sh: Likewise.
* bootstrap: Likewise.
* README-hacking: Likewise.
</content>
</entry>
<entry>
<title>maint: generalize the development prerequisites docs</title>
<updated>2009-07-03T15:47:17Z</updated>
<author>
<name>Pádraig Brady</name>
<email>P@draigBrady.com</email>
</author>
<published>2009-07-02T08:51:34Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/coreutils/commit/?id=3e565eb3a6a6d8992489195f5c0fd84d4246b800'/>
<id>urn:sha1:3e565eb3a6a6d8992489195f5c0fd84d4246b800</id>
<content type='text'>
* README-hacking: Add a little more high level info and
merge notes on specific developer prerequisites into README-prereq
* README-prereq: Remove the Fedora 8 specific information
and generalize the information to be applicable to any system.
</content>
</entry>
<entry>
<title>doc: README-hacking tweak</title>
<updated>2009-06-23T14:54:38Z</updated>
<author>
<name>Jim Meyering</name>
<email>meyering@redhat.com</email>
</author>
<published>2009-06-23T14:54:38Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/coreutils/commit/?id=f9554bbe25bc7d979926628655713a9c0ddc6dbb'/>
<id>urn:sha1:f9554bbe25bc7d979926628655713a9c0ddc6dbb</id>
<content type='text'>
* README-hacking: Move the "While building..." sentence down
to where it belongs.
</content>
</entry>
<entry>
<title>doc: typo fix in README-hacking</title>
<updated>2009-06-20T12:48:59Z</updated>
<author>
<name>Jim Meyering</name>
<email>meyering@redhat.com</email>
</author>
<published>2009-06-20T12:48:59Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/coreutils/commit/?id=0975852c5036b54d6d1fa18574d11db5943fba21'/>
<id>urn:sha1:0975852c5036b54d6d1fa18574d11db5943fba21</id>
<content type='text'>
* README-hacking: Fix a typo.
Don't make building from a git-cloned tree sound so hard.
</content>
</entry>
<entry>
<title>doc: use newer URL for XZ utils</title>
<updated>2009-06-03T05:19:20Z</updated>
<author>
<name>Jim Meyering</name>
<email>meyering@redhat.com</email>
</author>
<published>2009-06-02T19:44:11Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/coreutils/commit/?id=a65957da7703accf4ad156485fe3f37129615272'/>
<id>urn:sha1:a65957da7703accf4ad156485fe3f37129615272</id>
<content type='text'>
* README-hacking: Use &lt;http://tukaani.org/xz/&gt;
* README-prereq: Mention xz, not lzma.
</content>
</entry>
<entry>
<title>maint: Document how to best to enable gcc warnings for developers</title>
<updated>2009-03-11T14:52:52Z</updated>
<author>
<name>Pádraig Brady</name>
<email>P@draigBrady.com</email>
</author>
<published>2009-03-11T12:09:08Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/coreutils/commit/?id=cf0bb5e05d89d9239a819b696a85532a582c8d38'/>
<id>urn:sha1:cf0bb5e05d89d9239a819b696a85532a582c8d38</id>
<content type='text'>
* README-hacking: Mention --enable-gcc-warnings configure option
* configure.ac: Don't scare developers away from using gcc warnings
</content>
</entry>
<entry>
<title>add missing copyright dates</title>
<updated>2009-02-18T13:07:30Z</updated>
<author>
<name>Eric Blake</name>
<email>ebb9@byu.net</email>
</author>
<published>2009-02-18T13:07:30Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/coreutils/commit/?id=86cef85b3671ed0a14a444eef3b6cb07fa26ee64'/>
<id>urn:sha1:86cef85b3671ed0a14a444eef3b6cb07fa26ee64</id>
<content type='text'>
* NEWS: Add 2009 to copyright.
* README: Likewise.
* README-hacking: Likewise.
* TODO: Likewise.
* doc/Makefile.am: Likewise.
* m4/prereq.m4: Likewise.
* src/nl.c: Likewise.
* src/seq.c: Likewise.
* tests/cp/cp-i: Likewise.
* tests/install/install-C: Likewise.
* tests/install/install-C-root: Likewise.
* tests/install/install-C-selinux: Likewise.
* tests/misc/seq: Likewise.
* tests/mv/mv-n: Likewise.
</content>
</entry>
<entry>
<title>maint: mention how to run a single test in HACKING docs</title>
<updated>2009-02-13T11:13:33Z</updated>
<author>
<name>Pádraig Brady</name>
<email>P@draigBrady.com</email>
</author>
<published>2009-02-12T13:51:03Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/coreutils/commit/?id=48cae1e8642684f0103848b84d5884d1ba2412c8'/>
<id>urn:sha1:48cae1e8642684f0103848b84d5884d1ba2412c8</id>
<content type='text'>
* HACKING: Give an example of how to run a test in isolation.
* README: Fix/simplify example for running a single test.
* README-hacking: Reference the HACKING file.
</content>
</entry>
<entry>
<title>build: use dist-xz, not dist-lzma, cont'd</title>
<updated>2009-01-19T12:47:04Z</updated>
<author>
<name>Jim Meyering</name>
<email>meyering@redhat.com</email>
</author>
<published>2008-11-30T18:35:10Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/coreutils/commit/?id=9a45c1966716be7f02f8e20f014af720b69aa6fb'/>
<id>urn:sha1:9a45c1966716be7f02f8e20f014af720b69aa6fb</id>
<content type='text'>
* README-hacking: mention XZ utils
* README-prereq: Add a FIXME comment.
</content>
</entry>
<entry>
<title>Add better checks and docs for build tools</title>
<updated>2008-10-22T15:31:57Z</updated>
<author>
<name>Pádraig Brady</name>
<email>P@draigBrady.com</email>
</author>
<published>2008-10-21T21:40:12Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/coreutils/commit/?id=99f49949825acc53ae3f0a711ea3e8f96699442d'/>
<id>urn:sha1:99f49949825acc53ae3f0a711ea3e8f96699442d</id>
<content type='text'>
Prompted by a report from Ed Avis:
&lt;http://thread.gmane.org/gmane.comp.gnu.coreutils.bugs/14710&gt;

* README-hacking: Organise LZMA and Valgrind as
as optional requirements rather than in their own sections.
Mention bootstrap will now check tool versions.
* README-prereq: Make a start on specific instructions
for optaining build tools. Currently we just have notes
for Fedora linux.
* bootstrap.conf: Add the list of tools and versions required.
* bootstrap: Add the logic to check for the required tools,
and list all required tools and versions if any are missing.
</content>
</entry>
</feed>
