shred

August 25th, 2010



SYNOPSIS
shred [OPTIONS] FILE [...]

DESCRIPTION
Overwrite the specified FILE(s) repeatedly, in order to make it harder
for even very expensive hardware probing to recover the data.

Mandatory arguments to long options are mandatory for short options
too.

-f, –force
change permissions to allow writing if necessary

-n, –iterations=N
Overwrite N times instead of the default (25)

–random-source=FILE
get random bytes from FILE (default /dev/urandom)

-s, –size=N
shred this many bytes (suffixes like K, M, G accepted)

-u, –remove
truncate and remove file after overwriting

-v, –verbose
show progress

-x, –exact
do not round file sizes up to the next full block;

this is the default for non-regular files

-z, –zero
add a final overwrite with zeros to hide shredding

–help display this help and exit

–version
output version information and exit

If FILE is -, shred standard output.

Delete FILE(s) if –remove (-u) is specified. The default is not to
remove the files because it is common to operate on device files like
/dev/hda, and those files usually should not be removed. When operat-
ing on regular files, most people use the –remove option.

CAUTION: Note that shred relies on a very important assumption: that
the file system overwrites data in place. This is the traditional way
to do things, but many modern file system designs do not satisfy this
assumption. The following are examples of file systems on which shred

* compressed file systems

In the case of ext3 file systems, the above disclaimer applies (and
shred is thus of limited effectiveness) only in data=journal mode,
which journals file data in addition to just metadata. In both the
data=ordered (default) and data=writeback modes, shred works as usual.
Ext3 journaling modes can be changed by adding the data=something
option to the mount options for a particular file system in the
/etc/fstab file, as documented in the mount man page (man mount).

In addition, file system backups and remote mirrors may contain copies
of the file that cannot be removed, and that will allow a shredded file
to be recovered later.

AUTHOR
Written by Colin Plumb.

REPORTING BUGS
Report bugs to <bug-coreutils@gnu.org>.

COPYRIGHT
Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU
GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

SEE ALSO
The full documentation for shred is maintained as a Texinfo manual. If
the info and shred programs are properly installed at your site, the
command

info shred

should give you access to the complete manual.

GNU coreutils 6.9.92.4-f088d-dirtJanuary 2008 SHRED(1)

gzip

August 24th, 2010



SYNOPSIS
gzip [ -acdfhlLnNrtvV19 ] [-S suffix] [ name ... ]
gunzip [ -acfhlLnNrtvV ] [-S suffix] [ name ... ]
zcat [ -fhLV ] [ name ... ]

DESCRIPTION
Gzip reduces the size of the named files using Lempel-Ziv coding
(LZ77). Whenever possible, each file is replaced by one with the
extension .gz, while keeping the same ownership modes, access and modi-
fication times. (The default extension is -gz for VMS, z for MSDOS,
OS/2 FAT, Windows NT FAT and Atari.) If no files are specified, or if
a file name is “-”, the standard input is compressed to the standard
output. Gzip will only attempt to compress regular files. In particu-
lar, it will ignore symbolic links.

If the compressed file name is too long for its file system, gzip trun-
cates it. Gzip attempts to truncate only the parts of the file name
longer than 3 characters. (A part is delimited by dots.) If the name
consists of small parts only, the longest parts are truncated. For
example, if file names are limited to 14 characters, gzip.msdos.exe is
compressed to gzi.msd.exe.gz. Names are not truncated on systems which
do not have a limit on file name length.

By default, gzip keeps the original file name and timestamp in the com-
pressed file. These are used when decompressing the file with the -N
option. This is useful when the compressed file name was truncated or
when the time stamp was not preserved after a file transfer.

Compressed files can be restored to their original form using gzip -d
or gunzip or zcat. If the original name saved in the compressed file
is not suitable for its file system, a new name is constructed from the
original one to make it legal.

gunzip takes a list of files on its command line and replaces each file
whose name ends with .gz, -gz, .z, -z, _z or .Z and which begins with
the correct magic number with an uncompressed file without the original
extension. gunzip also recognizes the special extensions .tgz and .taz
as shorthands for .tar.gz and .tar.Z respectively. When compressing,
gzip uses the .tgz extension if necessary instead of truncating a file
with a .tar extension.

gunzip can currently decompress files created by gzip, zip, compress,
compress -H or pack. The detection of the input format is automatic.
When using the first two formats, gunzip checks a 32 bit CRC. For pack,
gunzip checks the uncompressed length. The standard compress format was
not designed to allow consistency checks. However gunzip is sometimes
able to detect a bad .Z file. If you get an error when uncompressing a
.Z file, do not assume that the .Z file is correct simply because the
standard uncompress does not complain. This generally means that the
standard uncompress does not check its input, and happily generates
garbage output. The SCO compress -H format (lzh compression method)
does not include a CRC but also allows some consistency checks.

Gzip uses the Lempel-Ziv algorithm used in zip and PKZIP. The amount
of compression obtained depends on the size of the input and the dis-
tribution of common substrings. Typically, text such as source code or
English is reduced by 60-70%. Compression is generally much better
than that achieved by LZW (as used in compress), Huffman coding (as
used in pack), or adaptive Huffman coding (compact).

Compression is always performed, even if the compressed file is
slightly larger than the original. The worst case expansion is a few
bytes for the gzip file header, plus 5 bytes every 32K block, or an
expansion ratio of 0.015% for large files. Note that the actual number
of used disk blocks almost never increases. gzip preserves the mode,
ownership and timestamps of files when compressing or decompressing.

The gzip file format is specified in P. Deutsch, GZIP file format spec-
ification version 4.3, <ftp://ftp.isi.edu/in-notes/rfc1952.txt>, Inter-
net RFC 1952 (May 1996). The zip deflation format is specified in P.
Deutsch, DEFLATE Compressed Data Format Specification version 1.3,
<ftp://ftp.isi.edu/in-notes/rfc1951.txt>, Internet RFC 1951 (May 1996).

OPTIONS
-a –ascii
Ascii text mode: convert end-of-lines using local conventions.
This option is supported only on some non-Unix systems. For
MSDOS, CR LF is converted to LF when compressing, and LF is con-
verted to CR LF when decompressing.

-c –stdout –to-stdout
Write output on standard output; keep original files unchanged.
If there are several input files, the output consists of a
sequence of independently compressed members. To obtain better
compression, concatenate all input files before compressing
them.

-d –decompress –uncompress
Decompress.

-f –force
Force compression or decompression even if the file has multiple
links or the corresponding file already exists, or if the com-
pressed data is read from or written to a terminal. If the input
data is not in a format recognized by gzip, and if the option
–stdout is also given, copy the input data without change to
the standard output: let zcat behave as cat. If -f is not
given, and when not running in the background, gzip prompts to
verify whether an existing file should be overwritten.

-h –help
Display a help screen and quit.

In combination with the –verbose option, the following fields
are also displayed:

method: compression method
crc: the 32-bit CRC of the uncompressed data
date & time: time stamp for the uncompressed file

The compression methods currently supported are deflate, com-
press, lzh (SCO compress -H) and pack. The crc is given as
ffffffff for a file not in gzip format.

With –name, the uncompressed name, date and time are those
stored within the compress file if present.

With –verbose, the size totals and compression ratio for all
files is also displayed, unless some sizes are unknown. With
–quiet, the title and totals lines are not displayed.

-L –license
Display the gzip license and quit.

-n –no-name
When compressing, do not save the original file name and time
stamp by default. (The original name is always saved if the name
had to be truncated.) When decompressing, do not restore the
original file name if present (remove only the gzip suffix from
the compressed file name) and do not restore the original time
stamp if present (copy it from the compressed file). This option
is the default when decompressing.

-N –name
When compressing, always save the original file name and time
stamp; this is the default. When decompressing, restore the
original file name and time stamp if present. This option is
useful on systems which have a limit on file name length or when
the time stamp has been lost after a file transfer.

-q –quiet
Suppress all warnings.

-r –recursive
Travel the directory structure recursively. If any of the file
names specified on the command line are directories, gzip will
descend into the directory and compress all the files it finds
there (or decompress them in the case of gunzip ).

–rsyncable
While compressing, synchronize the output occasionally based on
the input. This increases size by less than 1 percent most
cases, but means that the rsync(1) program can much more effi-
ciently synchronize files compressed with this flag. gunzip
cannot tell the difference between a compressed file created

-t –test
Test. Check the compressed file integrity.

-v –verbose
Verbose. Display the name and percentage reduction for each file
compressed or decompressed.

-V –version
Version. Display the version number and compilation options then
quit.

-# –fast –best
Regulate the speed of compression using the specified digit #,
where -1 or –fast indicates the fastest compression method
(less compression) and -9 or –best indicates the slowest com-
pression method (best compression). The default compression
level is -6 (that is, biased towards high compression at expense
of speed).

ADVANCED USAGE
Multiple compressed files can be concatenated. In this case, gunzip
will extract all members at once. For example:

gzip -c file1 > foo.gz
gzip -c file2 >> foo.gz

Then

gunzip -c foo

is equivalent to

cat file1 file2

In case of damage to one member of a .gz file, other members can still
be recovered (if the damaged member is removed). However, you can get
better compression by compressing all members at once:

cat file1 file2 | gzip > foo.gz

compresses better than

gzip -c file1 file2 > foo.gz

If you want to recompress concatenated files to get better compression,
do:

gzip -cd old.gz | gzip > new.gz

If a compressed file consists of several members, the uncompressed size
and CRC reported by the –list option applies to the last member only.
If you need the uncompressed size for all members, you can use:
for MSDOS: set GZIP=-8v –name

On Vax/VMS, the name of the environment variable is GZIP_OPT, to avoid
a conflict with the symbol set for invocation of the program.

SEE ALSO
znew(1), zcmp(1), zmore(1), zforce(1), gzexe(1), zip(1), unzip(1), com-
press(1), pack(1), compact(1)

The gzip file format is specified in P. Deutsch, GZIP file format spec-
ification version 4.3, <ftp://ftp.isi.edu/in-notes/rfc1952.txt>, Inter-
net RFC 1952 (May 1996). The zip deflation format is specified in P.
Deutsch, DEFLATE Compressed Data Format Specification version 1.3,
<ftp://ftp.isi.edu/in-notes/rfc1951.txt>, Internet RFC 1951 (May 1996).

DIAGNOSTICS
Exit status is normally 0; if an error occurs, exit status is 1. If a
warning occurs, exit status is 2.

Usage: gzip [-cdfhlLnNrtvV19] [-S suffix] [file ...]
Invalid options were specified on the command line.

file: not in gzip format
The file specified to gunzip has not been compressed.

file: Corrupt input. Use zcat to recover some data.
The compressed file has been damaged. The data up to the point
of failure can be recovered using

zcat file > recover

file: compressed with xx bits, can only handle yy bits
File was compressed (using LZW) by a program that could deal
with more bits than the decompress code on this machine. Recom-
press the file with gzip, which compresses better and uses less
memory.

file: already has .gz suffix — no change
The file is assumed to be already compressed. Rename the file
and try again.

file already exists; do you wish to overwrite (y or n)?
Respond “y” if you want the output file to be replaced; “n” if
not.

gunzip: corrupt input
A SIGSEGV violation was detected which usually means that the
input file has been corrupted.

xx.x% Percentage of the input saved by compression.
(Relevant only for -v and -l.)

and emits a warning by default. You have to use the –quiet option to
suppress the warning. This option can be set in the GZIP environment
variable as in:
for sh: GZIP=”-q” tar -xfz –block-compress /dev/rst0
for csh: (setenv GZIP -q; tar -xfz –block-compr /dev/rst0

In the above example, gzip is invoked implicitly by the -z option of
GNU tar. Make sure that the same block size (-b option of tar) is used
for reading and writing compressed data on tapes. (This example
assumes you are using the GNU version of tar.)

BUGS
The gzip format represents the input size modulo 2^32, so the –list
option reports incorrect uncompressed sizes and compression ratios for
uncompressed files 4 GB and larger. To work around this problem, you
can use the following command to discover a large uncompressed file’s
true size:

zcat file.gz | wc -c

The –list option reports sizes as -1 and crc as ffffffff if the com-
pressed file is on a non seekable media.

In some rare cases, the –best option gives worse compression than the
default compression level (-6). On some highly redundant files, com-
press compresses better than gzip.

COPYRIGHT NOTICE
Copyright (C) 1998, 1999, 2001, 2002 Free Software Foundation, Inc.
Copyright (C) 1992, 1993 Jean-loup Gailly

Permission is granted to make and distribute verbatim copies of this
manual provided the copyright notice and this permission notice are
preserved on all copies.

Permission is granted to copy and distribute modified versions of this
manual under the conditions for verbatim copying, provided that the
entire resulting derived work is distributed under the terms of a per-
mission notice identical to this one.

Permission is granted to copy and distribute translations of this man-
ual into another language, under the above conditions for modified ver-
sions, except that this permission notice may be stated in a transla-
tion approved by the Foundation.

local GZIP(1)

git-gc

August 23rd, 2010



SYNOPSIS
git-gc [--aggressive] [--auto] [--quiet]

DESCRIPTION
Runs a number of housekeeping tasks within the current repository, such
as compressing file revisions (to reduce disk space and increase
performance) and removing unreachable objects which may have been
created from prior invocations of git-add(1).

Users are encouraged to run this task on a regular basis within each
repository to maintain good disk space utilization and good operating
performance.

Some git commands may automatically run git-gc; see the –auto flag
below for details. If you know what you’re doing and all you want is to
disable this behavior permanently without further considerations, just
do:

$ git config –global gc.auto 0

OPTIONS
–aggressive
Usually git-gc runs very quickly while providing good disk space
utilization and performance. This option will cause git-gc to more
aggressively optimize the repository at the expense of taking much
more time. The effects of this optimization are persistent, so this
option only needs to be used occasionally; every few hundred
changesets or so.

–auto
With this option, git gc checks whether any housekeeping is
required; if not, it exits without performing any work. Some git
commands run git gc –auto after performing operations that could
create many loose objects.

Housekeeping is required if there are too many loose objects or too
many packs in the repository. If the number of loose objects
exceeds the value of the gc.auto configuration variable, then all
loose objects are combined into a single pack using git-repack -d
-l. Setting the value of gc.auto to 0 disables automatic packing of
loose objects.

If the number of packs exceeds the value of gc.autopacklimit, then
existing packs (except those marked with a .keep file) are
consolidated into a single pack by using the -A option of
git-repack. Setting gc.autopacklimit to 0 disables automatic
consolidation of packs.

–quiet
Suppress all progress reports.

users will want to expire them sooner. This option defaults to 30 days.

The optional configuration variable gc.rerereresolved indicates how
long records of conflicted merge you resolved earlier are kept. This
defaults to 60 days.

The optional configuration variable gc.rerereunresolved indicates how
long records of conflicted merge you have not resolved are kept. This
defaults to 15 days.

The optional configuration variable gc.packrefs determines if git gc
runs git-pack-refs. This can be set to “nobare” to enable it within all
non-bare repos or it can be set to a boolean value. This defaults to
true.

The optional configuration variable gc.aggressiveWindow controls how
much time is spent optimizing the delta compression of the objects in
the repository when the –aggressive option is specified. The larger
the value, the more time is spent optimizing the delta compression. See
the documentation for the –window’ option in git-repack(1) for more
details. This defaults to 10.

The optional configuration variable gc.pruneExpire controls how old the
unreferenced loose objects have to be before they are pruned. The
default is “2 weeks ago”.

NOTES
git-gc tries very hard to be safe about the garbage it collects. In
particular, it will keep not only objects referenced by your current
set of branches and tags, but also objects referenced by the index,
remote tracking branches, refs saved by git-filter-branch(1) in
refs/original/, or reflogs (which may references commits in branches
that were later amended or rewound).

If you are expecting some objects to be collected and they aren’t,
check all of those locations and decide whether it makes sense in your
case to remove those references.

SEE ALSO
git-prune(1) git-reflog(1) git-repack(1) git-rerere(1)

AUTHOR
Written by Shawn O. Pearce <spearce@spearce.org[1]>

GIT
Part of the git(1) suite

automake-1

August 22nd, 2010



SYNOPSIS
automake [ -a | --add-missing ] [ --amdir=DIR ] [ --build-dir=DIR ] [
-c | --copy ] [ --cygnus ] [ -f | --force-missing ] [ --foreign ] [
--gnits ] [ --gnu ] [ --help ] [ -i | --ignore-deps ] [ --include-deps
] [ --no-force ] [ -o DIR ] [ --output-dir=DIR ] [ --srcdir-name=DIR ]
[ -v | --verbose ] [ --version ] [ --Werror | --Wno-error ]

DESCRIPTION
To create all the Makefile.ins for a package, run the automake program
in the top level directory, with no arguments. automake will automati-
cally find each appropriate Makefile.am (by scanning configure.in) and
generate the corresponding Makefile.in. Note that automake has a
rather simplistic view of what constitutes a package; it assumes that a
package has only one configure.in, at the top. If your package has
multiple configure.ins, then you must run automake in each directory
holding a configure.in.

You can optionally give automake an argument; .am is appended to the
argument and the result is used as the name of the input file. This
feature is generally only used to automatically rebuild an out-of-date
Makefile.in. Note that automake must always be run from the topmost
directory of a project, even if being used to regenerate the Make-
file.in in some subdirectory. This is necessary because automake must
scan configure.in, and because automake uses the knowledge that a Make-
file.in is in a subdirectory to change its behavior in some cases.

automake accepts the following options:

-a

–add-missing
Automake requires certain common files to exist in certain situ-
ations; for instance config.guess is required if configure.in
runs AC_CANONICAL_HOST. Automake is distributed with several of
these files; this option will cause the missing ones to be auto-
matically added to the package, whenever possible. In general
if Automake tells you a file is missing, try using this option.
By default Automake tries to make a symbolic link pointing to
its own copy of the missing file; this can be changed with
–copy.

–libdir=DIR
Look for Automake data files in directory DIR instead of in the
installation directory. This is typically used for debugging.

-c

–copy When used with –add-missing, causes installed files to be
copied. The default is to make a symbolic link.

–cygnus
Causes the generated Makefile.ins to follow Cygnus rules,
Set the global strictness to gnits.

–gnu Set the global strictness to gnu. This is the default strict-
ness.

–help Print a summary of the command line options and exit.

-i

–ignore-deps
This disables the dependency tracking feature.

–include-deps
This enables the dependency tracking feature. This feature is
enabled by default. This option is provided for historical rea-
sons only and probably should not be used.

–no-force
Ordinarily automake creates all Makefile.ins mentioned in con-
figure.in. This option causes it to only update those Make-
file.ins which are out of date with respect to one of their
dependents.

-o DIR

–output-dir=DIR
Put the generated Makefile.in in the directory DIR. Ordinarily
each Makefile.in is created in the directory of the correspond-
ing Makefile.am. This option is used when making distributions.

-v

–verbose
Cause Automake to print information about which files are being
read or created.

–version
Print the version number of Automake and exit.

–Werror

–Wno-error
–Werror will cause all warnings issued by automake to become
errors. Errors affect the exit status of automake, while warn-
ings do not. –Wno-error, the default, causes warning to be
treated as warnings only.

SEE ALSO
aclocal(1), and the Texinfo documentation for automake

AUTHORS

resolveip

August 21st, 2010



SYNOPSIS
resolveip [options] {host_name|ip-addr} …

DESCRIPTION
The resolveip utility resolves hostnames to IP addresses and vice
versa.

Invoke resolveip like this:

shell> resolveip [options] {host_name|ip-addr} …

resolveip understands the options described in the following list.

o –help, -info, -?, -I

Display a help message and exit.

o –silent, -s

Silent mode. Produce less output.

o –version, -V

Display version information and exit.

COPYRIGHT
Copyright 2007-2008 MySQL AB

This documentation is free software; you can redistribute it and/or
modify it under the terms of the GNU General Public License as
published by the Free Software Foundation; version 2 of the License.

This documentation is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
General Public License for more details.

You should have received a copy of the GNU General Public License along
with the program; if not, write to the Free Software Foundation, Inc.,
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA or see
http://www.gnu.org/licenses/.

SEE ALSO
For more information, please refer to the MySQL Reference Manual, which
may already be installed locally and which is also available online at
http://dev.mysql.com/doc/.

AUTHOR
MySQL AB (http://www.mysql.com/).

cmuwmtopbm

August 20th, 2010



SYNOPSIS
cmuwmtopbm [cmuwmfile]

DESCRIPTION
Reads a CMU window manager bitmap as input. Produces a portable bitmap
as output.

SEE ALSO
pbmtocmuwm(1), pbm(5)

AUTHOR
Copyright (C) 1989 by Jef Poskanzer.

15 April 1989 cmuwmtopbm(1)

git-show

August 19th, 2010



SYNOPSIS
git-show [options] <object>…

DESCRIPTION
Shows one or more objects (blobs, trees, tags and commits).

For commits it shows the log message and textual diff. It also presents
the merge commit in a special format as produced by git-diff-tree –cc.

For tags, it shows the tag message and the referenced objects.

For trees, it shows the names (equivalent to git-ls-tree(1) with
–name-only).

For plain blobs, it shows the plain contents.

The command takes options applicable to the git-diff-tree(1) command to
control how the changes the commit introduces are shown.

This manual page describes only the most frequently used options.

OPTIONS
<object>
The name of the object to show. For a more complete list of ways to
spell object names, see “SPECIFYING REVISIONS” section in git-rev-
parse(1).

–pretty[=<format>]
Pretty-print the contents of the commit logs in a given format,
where <format> can be one of oneline, short, medium, full, fuller,
email, raw and format:<string>. When omitted, the format defaults
to medium.

Note: you can specify the default pretty format in the repository
configuration (see git-config(1)).

–abbrev-commit
Instead of showing the full 40-byte hexadecimal commit object name,
show only handful hexdigits prefix. Non default number of digits
can be specified with “–abbrev=<n>” (which also modifies diff
output, if it is displayed).

This should make “–pretty=oneline” a whole lot more readable for
people using 80-column terminals.

–encoding[=<encoding>]
The commit objects record the encoding used for the log message in
their encoding header; this option can be used to tell the command
to re-code the commit log message in the encoding preferred by the
user. For non plumbing commands this defaults to UTF-8.

<sha1> <title line>
This is designed to be as compact as possible.

o short

commit <sha1>
Author: <author>

<title line>

o medium

commit <sha1>
Author: <author>
Date: <author date>

<title line>

<full commit message>

o full

commit <sha1>
Author: <author>
Commit: <committer>

<title line>

<full commit message>

o fuller

commit <sha1>
Author: <author>
AuthorDate: <author date>
Commit: <committer>
CommitDate: <committer date>

<title line>

<full commit message>

o email

From <sha1> <date>
From: <author>
Date: <author date>
Subject: [PATCH] <title line>

<full commit message>

E.g, format:”The author of %h was %an, %ar%nThe title was >>%s<<%n”
would show something like this:

The author of fe6e0ee was Junio C Hamano, 23 hours ago
The title was >>t4119: test autocomputing -p<n> for traditional diff input.<<
The placeholders are:

o %H: commit hash

o %h: abbreviated commit hash

o %T: tree hash

o %t: abbreviated tree hash

o %P: parent hashes

o %p: abbreviated parent hashes

o %an: author name

o %aN: author name (respecting .mailmap)

o %ae: author email

o %ad: author date

o %aD: author date, RFC2822 style

o %ar: author date, relative

o %at: author date, UNIX timestamp

o %ai: author date, ISO 8601 format

o %cn: committer name

o %cN: committer name (respecting .mailmap)

o %ce: committer email

o %cd: committer date

o %cD: committer date, RFC2822 style

o %cr: committer date, relative

o %ct: committer date, UNIX timestamp

o %ci: committer date, ISO 8601 format

o %e: encoding

o %n: newline

o %x00: print a byte from a hex code

o tformat:

The tformat: format works exactly like format:, except that it
provides “terminator” semantics instead of “separator” semantics.
In other words, each commit has the message terminator character
(usually a newline) appended, rather than a separator placed
between entries. This means that the final entry of a single-line
format will be properly terminated with a new line, just as the
“oneline” format does. For example:

$ git log -2 –pretty=format:%h 4da45bef \
| perl -pe ‘$_ .= ” — NO NEWLINE\n” unless /\n/’
4da45be
7134973 — NO NEWLINE

$ git log -2 –pretty=tformat:%h 4da45bef \
| perl -pe ‘$_ .= ” — NO NEWLINE\n” unless /\n/’
4da45be
7134973

EXAMPLES
git show v1.0.0
Shows the tag v1.0.0, along with the object the tags points at.

git show v1.0.0^{tree}
Shows the tree pointed to by the tag v1.0.0.

git show next~10:Documentation/README
Shows the contents of the file Documentation/README as they were
current in the 10th last commit of the branch next.

git show master:Makefile master:t/Makefile
Concatenates the contents of said Makefiles in the head of the
branch master.

DISCUSSION
At the core level, git is character encoding agnostic.

o The pathnames recorded in the index and in the tree objects are
treated as uninterpreted sequences of non-NUL bytes. What
readdir(2) returns are what are recorded and compared with the data
git keeps track of, which in turn are expected to be what lstat(2)
and creat(2) accepts. There is no such thing as pathname encoding
translation.

o The contents of the blob objects are uninterpreted sequence of
legacy encoding. The way to say this is to have i18n.commitencoding
in .git/config file, like this:

[i18n]
commitencoding = ISO-8859-1
Commit objects created with the above setting record the value of
i18n.commitencoding in its encoding header. This is to help other
people who look at them later. Lack of this header implies that the
commit log message is encoded in UTF-8.

2. git-log, git-show and friends looks at the encoding header of a
commit object, and tries to re-code the log message into UTF-8
unless otherwise specified. You can specify the desired output
encoding with i18n.logoutputencoding in .git/config file, like
this:

[i18n]
logoutputencoding = ISO-8859-1
If you do not have this configuration variable, the value of
i18n.commitencoding is used instead.
Note that we deliberately chose not to re-code the commit log message
when a commit is made to force UTF-8 at the commit object level,
because re-coding to UTF-8 is not necessarily a reversible operation.

AUTHOR
Written by Linus Torvalds <torvalds@osdl.org[1]> and Junio C Hamano
<gitster@pobox.com[2]>. Significantly enhanced by Johannes Schindelin
<Johannes.Schindelin@gmx.de[3]>.

DOCUMENTATION
Documentation by David Greaves, Petr Baudis and the git-list
<git@vger.kernel.org[4]>.

GIT
Part of the git(1) suite

NOTES
1. torvalds@osdl.org
mailto:torvalds@osdl.org

2. gitster@pobox.com
mailto:gitster@pobox.com

3. Johannes.Schindelin@gmx.de
mailto:Johannes.Schindelin@gmx.de

4. git@vger.kernel.org
mailto:git@vger.kernel.org

git-fmt-merge-msg

August 18th, 2010



SYNOPSIS
git-fmt-merge-msg [--log | --no-log] <$GIT_DIR/FETCH_HEAD
git-fmt-merge-msg [--log | --no-log] -F <file>

DESCRIPTION
Takes the list of merged objects on stdin and produces a suitable
commit message to be used for the merge commit, usually to be passed as
the <merge-message> argument of git-merge.

This script is intended mostly for internal use by scripts
automatically invoking git-merge.

OPTIONS
–log
In addition to branch names, populate the log message with one-line
descriptions from the actual commits that are being merged.

–no-log
Do not list one-line descriptions from the actual commits being
merged.

–summary, –no-summary
Synonyms to –log and –no-log; these are deprecated and will be
removed in the future.

-F <file>, –file <file>
Take the list of merged objects from <file> instead of stdin.

CONFIGURATION
merge.log
Whether to include summaries of merged commits in newly merge
commit messages. False by default.

merge.summary
Synonym to merge.log; this is deprecated and will be removed in the
future.

SEE ALSO
git-merge(1)

AUTHOR
Written by Junio C Hamano <gitster@pobox.com[1]>

DOCUMENTATION
Documentation by Petr Baudis, Junio C Hamano and the git-list
<git@vger.kernel.org[2]>.

GIT

locale

August 17th, 2010



SYNOPSIS
locale [ -a | -m]

locale [ -ck ] name…

DESCRIPTION
The locale program writes information about the current locale environ-
ment, or all locales, to standard output.

When invoked without arguments, locale summarizes the current locale
environment for each locale category defined by the LC_* environment
variables.

-a, –all-locales

Write names of available locales.

-m, –charmaps

Write names of available charmaps.

Output Format:

-c, –category-name

Write names of selected categories.

-k, –keyword-name

Write names and values of selected keywords.

ENVIRONMENT VARIABLES
These environment variables affect each locale categories for all
locale-aware programs:

LC_CTYPE

Character classification and case conversion.

LC_COLLATE

Collation order.

LC_TIME

Date and time formats.

LC_NUMERIC

Non-monetary numeric formats.

LC_NAME

Name formats.

LC_ADDRESS

Address formats and location information.

LC_TELEPHONE

Telephone number formats.

LC_MEASUREMENT

Measurement units (Metric or Other).

LC_IDENTIFICATION

Metadata about the locale information.

This environment variable can switch against multiple locale database:

LOCPATH

The directory where locale data is stored. By default, /usr/lib/locale is used.

FILES
/usr/share/i18n/SUPPORTED
List of supported values (and their associated encoding) for
the locale name. This representation is recommended over
–all-locales one, due being the system wide supported values.

AUTHOR
locale was written by Ulrich Drepper for the GNU C Library.
This manpage was written by Joel Klecker <espy@debian.org> for the
Debian GNU/Linux system, and expanded by Alastair McKinstry <mck-
instry@computer.org>

SEE ALSO
locale(5), locale(7), setlocale(3)

3rd Berkeley Distribution 2004-12-16 LOCALE(1)

gsbj

August 16th, 2010



gsdj - Format and print text for DeskJet printer using ghostscript
gsdj500 - Format and print text for DeskJet 500 BubbleJet using
ghostscript
gslj - Format and print text for LaserJet printer using ghostscript

SYNOPSIS
gslp -12BclqRr -b<header> -f<font> -F<hfont> -L<lines> -p<outfile>
-T<n> –add-to-space <units> –add-to-width <units> –columns <n>
–detect –first-page <n> –kern <file.afm> –last-page <n> –(head-
ing|footing)-(left|center|right) <string> –margin-(top|bot-
tom|left|right) <inches> –no-eject-(file|formfeed) –spacing <n>
[gs options] [files]
gsbj [options] [files]
gsdj [options] [files]
gsdj500 [options] [files]
gslj [options] [files]

DESCRIPTION
This utility provides functionality approximately equivalent to the
Unix enscript(1) program. It prints plain text files using a single
font. It currently handles tabs and formfeeds, but not backspaces. It
will line-wrap when using fixed-pitch fonts. It will also do kerning
and width adjustment.

The default device (-sDEVICE=) and resolution (-r) are as follows:
gslp epson 180
gsbj bj10e 180
gsdj deskjet 300
gsdj500 djet500 300
gslj laserjet 300
By default the current date is formatted as the center header.

OPTIONS
Standard switches implemented:
-12BclqRr -b<header> -f<font> -F<hfont> -L<lines> -p<outfile>

Sun switches implemented:
-T<n> set tab width

Switches ignored:
-GghKkmow -# -C -d -J -n -P -S -s -t -v

Switches added:

–add-to-space <units>
add the given number of 1/72″ units to the width of each
space (may be negative)

–add-to-width <units>
add the given number of 1/72″ units to the width of each
character (may be negative)

–(heading|footing)-(left|center|right) <string>
set the heading/footing fields; use -B first to clear

–margin-(top|bottom|left|right) <inches>
set a margin

–no-eject-(file|formfeed)
end-of-file/FF only starts a new column, not a new sheet

–spacing <n>
use double (n=2), triple (n=3), etc. spacing
Also, the string %# in a heading or footing is replaced with the page
#.

SEE ALSO
gs(1)

VERSION
This document was last revised for Ghostscript version 8.62.

AUTHOR
Artifex Software, Inc. are the primary maintainers of Ghostscript.
This manpage by George Ferguson.

8.62 29 February 2008 GSLP(1)