Git/commit - Revision history

Woozle: git log

2018-11-12T14:44:52Z

git log

← Older revision		Revision as of 14:44, 12 November 2018
Line 20:		Line 20:

	''The last two paragraphs were adapted from [http://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell 3.1 Git Branching - Branches in a Nutshell].''		''The last two paragraphs were adapted from [http://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell 3.1 Git Branching - Branches in a Nutshell].''
			==Related==
			* [[../log\|git log]] returns information about existing commits
	==Command==		==Command==
	===~~Links~~===		===Reference===
	* [https://www.kernel.org/pub/software/scm/git/docs/git-commit.html manpage]		* [https://www.kernel.org/pub/software/scm/git/docs/git-commit.html manpage]

Woozle: /* Command */ manual page link

2015-07-12T22:16:09Z

Command: manual page link

← Older revision		Revision as of 22:16, 12 July 2015
Line 21:		Line 21:
	''The last two paragraphs were adapted from [http://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell 3.1 Git Branching - Branches in a Nutshell].''		''The last two paragraphs were adapted from [http://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell 3.1 Git Branching - Branches in a Nutshell].''
	==Command==		==Command==
			===Links===
			* [https://www.kernel.org/pub/software/scm/git/docs/git-commit.html manpage]

Woozle: more details

2015-03-13T21:24:16Z

more details

← Older revision		Revision as of 21:24, 13 March 2015
Line 1:		Line 1:
	[[category:git/concepts\|commit]]		[[category:git/concepts\|commit]]
	"~~Committed~~" ~~seems to be~~ a ~~per~~-file ~~flag~~ that ~~indicates whether~~ a ~~{{l/same\|staged}} file~~ is ~~ready for further operations, such as {{l/same\|push}}ing. (There's some ambiguity about whether it makes sense to speak of files being "[un]modified", or whether that only applies to "changes" -- see~~ {{l/same\|~~notes~~}}.)		[[category:git/commands\|commit]]
			==Concept==
			"A commit" is a specific set of project-file revisions that are archived together at a specific time. A commit is created from what is currently in the {{l/same\|staging}} area.

	"~~A commit~~" is a ~~specific set of project~~-file ~~revisions~~ that ~~are archived together at~~ a ~~specific time~~.		"Committed" seems to be a per-file flag that indicates whether a {{l/same\|staged}} file is ready for further operations, such as {{l/same\|push}}ing.

	~~When you create a commit with [[..~~/~~commit~~\|~~git~~ commit]], Git checksums each subdirectory and stores those tree objects in the Git {{l/same\|repository}}. Git then creates a commit object that has the metadata and a pointer to the root project tree so it can re-create that snapshot when needed.		At {{l/same\|commit}} time, Git checksums each subdirectory (and file?) and stores those tree objects under the {{l/same\|HEAD}} {{l/same\|branch}} of the project's Git {{l/same\|repository}} (which is kept under the .git/ folder). Git then creates a commit object that has the metadata and a pointer to the root project tree so it can re-create that snapshot when needed.

	~~After committing, the {{l~~/~~same~~\|~~repository}} contains~~ the following objects:		When you create a commit with [[../commit\|git commit]], Git stores the following objects:
	* one blob for each of your files, containing that file's contents		* one blob for each of your files, containing that file's contents
	* one tree that lists the contents of the directory and specifies which file names are stored as which blobs		* one tree that lists the contents of the directory and specifies which file names are stored as which blobs
	* ~~one~~ commit ~~with~~ the ~~pointer~~ to that ~~root tree and all~~ the commit ~~metadata~~.		* a commit object, which is basically a pointer to the snapshot of the content you staged, which contains:
			** the author's name and email (from Git's configuration data)
			** the commit message that you typed when creating the commit
			** pointers to the commit or commits that directly came before this commit (its parent or parents)
			*** zero parents for the initial commit
			*** one parent for a normal commit
			*** multiple parents for a commit that results from a merge of two or more branches.

	''The last two paragraphs were adapted from [http://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell 3.1 Git Branching - Branches in a Nutshell].''		''The last two paragraphs were adapted from [http://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell 3.1 Git Branching - Branches in a Nutshell].''
			==Command==

Woozle: proper sorting for category

2015-03-09T21:11:07Z

proper sorting for category

← Older revision		Revision as of 21:11, 9 March 2015
Line 1:		Line 1:
	[[category:git/concepts]]		[[category:git/concepts\|commit]]
	"Committed" seems to be a per-file flag that indicates whether a {{l/same\|staged}} file is ready for further operations, such as {{l/same\|push}}ing. (There's some ambiguity about whether it makes sense to speak of files being "[un]modified", or whether that only applies to "changes" -- see {{l/same\|notes}}.)		"Committed" seems to be a per-file flag that indicates whether a {{l/same\|staged}} file is ready for further operations, such as {{l/same\|push}}ing. (There's some ambiguity about whether it makes sense to speak of files being "[un]modified", or whether that only applies to "changes" -- see {{l/same\|notes}}.)

Woozle: a bit more explanation from the book

2015-03-09T17:10:10Z

a bit more explanation from the book

← Older revision		Revision as of 17:10, 9 March 2015
Line 1:		Line 1:
	[[category:git/concepts]]		[[category:git/concepts]]
	"Committed" seems to be a per-file flag that indicates whether a {{l/same\|staged}} file is ready for further operations, such as {{l/same\|push}}ing. (There's some ambiguity about whether it makes sense to speak of files being "[un]modified", or whether that only applies to "changes" -- see {{l/same\|notes}}.)		"Committed" seems to be a per-file flag that indicates whether a {{l/same\|staged}} file is ready for further operations, such as {{l/same\|push}}ing. (There's some ambiguity about whether it makes sense to speak of files being "[un]modified", or whether that only applies to "changes" -- see {{l/same\|notes}}.)

			"A commit" is a specific set of project-file revisions that are archived together at a specific time.

			When you create a commit with [[../commit\|git commit]], Git checksums each subdirectory and stores those tree objects in the Git {{l/same\|repository}}. Git then creates a commit object that has the metadata and a pointer to the root project tree so it can re-create that snapshot when needed.

			After committing, the {{l/same\|repository}} contains the following objects:
			* one blob for each of your files, containing that file's contents
			* one tree that lists the contents of the directory and specifies which file names are stored as which blobs
			* one commit with the pointer to that root tree and all the commit metadata.

			''The last two paragraphs were adapted from [http://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell 3.1 Git Branching - Branches in a Nutshell].''

Woozle: attempt to sort this out

2015-03-09T15:01:18Z

attempt to sort this out

← Older revision		Revision as of 15:01, 9 March 2015
Line 1:		Line 1:
	[[category:git/concepts]]		[[category:git/concepts]]
	~~I don~~'~~t yet have a good definition~~ of a "~~commit~~".		"Committed" seems to be a per-file flag that indicates whether a {{l/same\|staged}} file is ready for further operations, such as {{l/same\|push}}ing. (There's some ambiguity about whether it makes sense to speak of files being "[un]modified", or whether that only applies to "changes" -- see {{l/same\|notes}}.)

Woozle: Created page with "category:git/concepts I don't yet have a good definition of a "commit"."

2015-03-09T14:00:03Z

Created page with "category:git/concepts I don't yet have a good definition of a "commit"."

New page

[[category:git/concepts]]
I don't yet have a good definition of a "commit".