Home Explore Blog CI



git

1st chunk of `Documentation/fsck-msgids.adoc`
910f60ac5f2b6ce41f5f8e7840193ed77582275eb020b2400000000100000c5d
`badDate`::
	(ERROR) Invalid date format in an author/committer line.

`badDateOverflow`::
	(ERROR) Invalid date value in an author/committer line.

`badEmail`::
	(ERROR) Invalid email format in an author/committer line.

`badFilemode`::
	(INFO) A tree contains a bad filemode entry.

`badName`::
	(ERROR) An author/committer name is empty.

`badObjectSha1`::
	(ERROR) An object has a bad sha1.

`badPackedRefEntry`::
	(ERROR) The "packed-refs" file contains an invalid entry.

`badPackedRefHeader`::
	(ERROR) The "packed-refs" file contains an invalid
	header.

`badParentSha1`::
	(ERROR) A commit object has a bad parent sha1.

`badRefContent`::
	(ERROR) A ref has bad content.

`badRefFiletype`::
	(ERROR) A ref has a bad file type.

`badRefName`::
	(ERROR) A ref has an invalid format.

`badReferentName`::
	(ERROR) The referent name of a symref is invalid.

`badTagName`::
	(INFO) A tag has an invalid format.

`badTimezone`::
	(ERROR) Found an invalid time zone in an author/committer line.

`badTree`::
	(ERROR) A tree cannot be parsed.

`badTreeSha1`::
	(ERROR) A tree has an invalid format.

`badType`::
	(ERROR) Found an invalid object type.

`duplicateEntries`::
	(ERROR) A tree contains duplicate file entries.

`emptyName`::
	(WARN) A path contains an empty name.

`emptyPackedRefsFile`::
	(INFO) "packed-refs" file is empty. Report to the
	git@vger.kernel.org mailing list if you see this error. As only
	very early versions of Git would create such an empty
	"packed_refs" file, we might tighten this rule in the future.

`extraHeaderEntry`::
	(IGNORE) Extra headers found after `tagger`.

`fullPathname`::
	(WARN) A path contains the full path starting with "/".

`gitattributesBlob`::
	(ERROR) A non-blob found at `.gitattributes`.

`gitattributesLarge`::
	(ERROR) The `.gitattributes` blob is too large.

`gitattributesLineLength`::
	(ERROR) The `.gitattributes` blob contains too long lines.

`gitattributesMissing`::
	(ERROR) Unable to read `.gitattributes` blob.

`gitattributesSymlink`::
	(INFO) `.gitattributes` is a symlink.

`gitignoreSymlink`::
	(INFO) `.gitignore` is a symlink.

`gitmodulesBlob`::
	(ERROR) A non-blob found at `.gitmodules`.

`gitmodulesLarge`::
	(ERROR) The `.gitmodules` file is too large to parse.

`gitmodulesMissing`::
	(ERROR) Unable to read `.gitmodules` blob.

`gitmodulesName`::
	(ERROR) A submodule name is invalid.

`gitmodulesParse`::
	(INFO) Could not parse `.gitmodules` blob.

`gitmodulesLarge`;
	(ERROR) `.gitmodules` blob is too large to parse.

`gitmodulesPath`::
	(ERROR) `.gitmodules` path is invalid.

`gitmodulesSymlink`::
	(ERROR) `.gitmodules` is a symlink.

`gitmodulesUpdate`::
	(ERROR) Found an invalid submodule update setting.

`gitmodulesUrl`::
	(ERROR) Found an invalid submodule url.

`hasDot`::
	(WARN) A tree contains an entry named `.`.

`hasDotdot`::
	(WARN) A tree contains an entry named `..`.

`hasDotgit`::
	(WARN) A tree contains an entry named `.git`.

`largePathname`::
	(WARN) A tree contains an entry with a very long path name. If
	the value of `fsck.largePathname` contains a colon, that value
	is used as the maximum allowable length (e.g., "warn:10" would
	complain about

Title: Git Error and Warning Messages
Summary
The text lists various error and warning messages related to Git, a version control system, including issues with file formats, invalid data, and improper configurations, with each message categorized by type, such as ERROR, WARN, or INFO.