freshlybakedca.ke
Git fork
1git-hash-object(1)
2==================
3
4NAME
5----
6git-hash-object - Compute object ID and optionally create an object from a file
7
8
9SYNOPSIS
10--------
11[verse]
12'git hash-object' [-t <type>] [-w] [--path=<file> | --no-filters]
13 [--stdin [--literally]] [--] <file>...
14'git hash-object' [-t <type>] [-w] --stdin-paths [--no-filters]
15
16DESCRIPTION
17-----------
18Computes the object ID value for an object with specified type
19with the contents of the named file (which can be outside of the
20work tree), and optionally writes the resulting object into the
21object database. Reports its object ID to its standard output.
22When <type> is not specified, it defaults to "blob".
23
24OPTIONS
25-------
26
27-t <type>::
28 Specify the type of object to be created (default: "blob"). Possible
29 values are `commit`, `tree`, `blob`, and `tag`.
30
31-w::
32 Actually write the object into the object database.
33
34--stdin::
35 Read the object from standard input instead of from a file.
36
37--stdin-paths::
38 Read file names from the standard input, one per line, instead
39 of from the command-line.
40
41--path::
42 Hash object as if it were located at the given path. The location of
43 the file does not directly influence the hash value, but the path is
44 used to determine which Git filters should be applied to the object
45 before it can be placed in the object database. As a result of
46 applying filters, the actual blob put into the object database may
47 differ from the given file. This option is mainly useful for hashing
48 temporary files located outside of the working directory or files
49 read from stdin.
50
51--no-filters::
52 Hash the contents as is, ignoring any input filter that would
53 have been chosen by the attributes mechanism, including the end-of-line
54 conversion. If the file is read from standard input then this
55 is always implied, unless the `--path` option is given.
56
57--literally::
58 Allow `--stdin` to hash any garbage into a loose object which might not
59 otherwise pass standard object parsing or git-fsck checks. Useful for
60 stress-testing Git itself or reproducing characteristics of corrupt or
61 bogus objects encountered in the wild.
62
63GIT
64---
65Part of the linkgit:git[1] suite