git@vger.kernel.org list mirror (unofficial, one of many)
 help / color / mirror / code / Atom feed
100630d0215ef5c88d2d26e51ca288a6c0c2b102 blob 2434 bytes (raw)

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
 
git-hash-object(1)
==================

NAME
----
git-hash-object - Compute object ID and optionally creates a blob from a file


SYNOPSIS
--------
[verse]
'git hash-object' [-t <type>] [-w] [--path=<file>|--no-filters] [--stdin [--literally]] [--] <file>...
'git hash-object' [-t <type>] [-w] --stdin-paths [--no-filters]

DESCRIPTION
-----------
Computes the object ID value for an object with specified type
with the contents of the named file (which can be outside of the
work tree), and optionally writes the resulting object into the
object database.  Reports its object ID to its standard output.
When <type> is not specified, it defaults to "blob".

OPTIONS
-------

-t <type>::
	Specify the type (default: "blob").

-w::
	Actually write the object into the object database.
+
No guarantees are made as to how the object is added to the database
(e.g. whether as a loose object, or streamed to a pack), except in the
case of the `--literally` option. How it's written may depend on
heuristics such as the `core.bigFileThreshold` configuration variable
(see linkgit:git-config[1]).

--stdin::
	Read the object from standard input instead of from a file.

--stdin-paths::
	Read file names from the standard input, one per line, instead
	of from the command-line.

--path::
	Hash object as it were located at the given path. The location of
	file does not directly influence on the hash value, but path is
	used to determine what Git filters should be applied to the object
	before it can be placed to the object database, and, as result of
	applying filters, the actual blob put into the object database may
	differ from the given file. This option is mainly useful for hashing
	temporary files located outside of the working directory or files
	read from stdin.

--no-filters::
	Hash the contents as is, ignoring any input filter that would
	have been chosen by the attributes mechanism, including the end-of-line
	conversion. If the file is read from standard input then this
	is always implied, unless the `--path` option is given.

--literally::
	Allow for hashing arbitrary data which might not
	otherwise pass standard object parsing or git-fsck checks. Useful for
	stress-testing Git itself or reproducing characteristics of corrupt or
	bogus objects encountered in the wild. When writing objects guarantees
	that the written object will be a loose object, for ease of debugging.

GIT
---
Part of the linkgit:git[1] suite
debug log:

solving 100630d021 ...
found 100630d021 in https://public-inbox.org/git/20190520215312.10363-3-avarab@gmail.com/
found df9e2c58bd in git.git.git
preparing index
index prepared:
100644 df9e2c58bdbc5f31edaf25577df744868e16f3de	Documentation/git-hash-object.txt

applying [1/1] https://public-inbox.org/git/20190520215312.10363-3-avarab@gmail.com/
diff --git a/Documentation/git-hash-object.txt b/Documentation/git-hash-object.txt
index df9e2c58bd..100630d021 100644

Checking patch Documentation/git-hash-object.txt...
Applied patch Documentation/git-hash-object.txt cleanly.

index at:
100644 100630d0215ef5c88d2d26e51ca288a6c0c2b102	Documentation/git-hash-object.txt

Code repositories for project(s) associated with this inbox:

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).