-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to jida...@jidanni.org on 1/17/2009 9:37 AM:
> Gentlemen, it dawned on me. coreutils.texi is too big, from a source
> code management point of view. It should be broken down into logical
> parts, one for stty, one for sort, etc. Then you can pull it all
> together via @includes. Anyway, it makes no sense for e.g., edits to
> stty invocation to conflict with edits to sort invocation.
But edits to distinct @node's within the document generally don't
conflict; git merge algorithms are generally good enough to not make that
a problem. In fact, I personally like having a monolithic document, as it
makes searching for similar text easier from the editor, rather than
having to fire up an external grep for everything in the directory.
But making one file per @node might not be too bad an idea; after all,
that is how gnulib's documentation is maintained. From an archeological
point of view, it is indeed easier to trace the history of a single node
if that node is isolated to its own file.
Care to submit a patch?
- --
Don't work too hard, make some time for fun as well!
Eric Blake e...@byu.net
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAklyMT4ACgkQ84KuGfSFAYABhQCgonOQt0kqwEj6SWv5316bFDDT
YJUAniMpISObwzs8JbJ/3wkJto8uvPEw
=Ptmx
-END PGP SIGNATURE-
___
Bug-coreutils mailing list
Bug-coreutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-coreutils
