[Discuss] Suse sed question

[markw at mohawksoft.com]

markw at sles11:~> sed -h
sed: invalid option -- 'h'
Usage: sed [OPTION]... {script-only-if-no-other-script} [input-file]...

  -n, --quiet, --silent
                 suppress automatic printing of pattern space
  -e script, --expression=script
                 add the script to the commands to be executed
  -f script-file, --file=script-file
                 add the contents of script-file to the commands to be
executed
  --follow-symlinks
                 follow symlinks when processing in place
  -i[SUFFIX], --in-place[=SUFFIX]
                 edit files in place (makes backup if extension supplied)
  -l N, --line-length=N
                 specify the desired line-wrap length for the `l' command
  --posix
                 disable all GNU extensions.
  -r, --regexp-extended
                 use extended regular expressions in the script.
  -s, --separate
                 consider files as separate rather than as a single
continuous
                 long stream.
  -u, --unbuffered
                 load minimal amounts of data from the input files and flush
                 the output buffers more often
      --help     display this help and exit
      --version  output version information and exit

If no -e, --expression, -f, or --file option is given, then the first
non-option argument is taken as the sed script to interpret.  All
remaining arguments are names of input files; if no input files are
specified, then the standard input is read.

E-mail bug reports to: bonzini at gnu.org .
Be sure to include the word ``sed'' somewhere in the ``Subject:'' field.
markw at sles11:~>


> I need to verify this for myself, but someone working with moving some dev
> continuous integration tools from Windows to an older version of Suse
> tells me that the sed command is missing the -b option to treat input
> files as binary.  Its taking all the input files, which are in DOS format,
> and converting them to POSIX line endings, which is causing our source
> control system to act as if every line in the file is changed.
>
> Can someone confirm this?
>
> _______________________________________________
> Discuss mailing list
> Discuss at blu.org
> http://lists.blu.org/mailman/listinfo/discuss
>