> From: [EMAIL PROTECTED] (Don Kitchen) >> > from the --help output and from a tee.x template file, so you would have >> > to rework your patch to hit the upstream source of the manpage. Also, >> >> Yes, I considered that, but the patch is easy to cut and paste from and >> shows the general idea. The important part is not even the particular >> text, the important part is to point out the command construct that >> basically gives tee a second standard out to pass to a second set of >> piped commands.
Thanks for the suggested documentation change. A good example would help. For example, you could show how to tee output to one process that would grep for something, while another (through a fifo) might save a compressed copy. While you may think it's easy just to paste a line into coreutils.texi, there's more to it than that. If you take the time to construct a useful example, create a proper unified diff showing your changes to the .texi file, and spend just a little more time to write a ChangeLog entry, I'll be more likely to apply your change. _______________________________________________ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils