Git notes - Revision history

Ted: Add subsection q branch maintenance q

2026-02-26T16:35:59Z

Add subsection q branch maintenance q

2026-01-28T22:01:50Z

Commit Signing

2026-01-24T06:23:19Z

Commit Signing : add link to forum post at Superuser dot com

2026-01-24T06:21:14Z

Add section q Commit Signing q, and note on export GPG_TTY

2026-01-22T16:07:27Z

Add notes on git log --name-only and git log --name-status

2026-01-08T00:09:45Z

git querying commands : link to Eduardo Silva Medium dot com article on git rev-parse

2025-12-29T17:58:03Z

Git notes : git rebase : amend notes for Enrico Campidoglio post about git rebase

2025-10-14T06:07:52Z

^ Git remotes

2025-07-24T17:58:33Z

git stash : add example git stash with commit-like note.

2025-07-08T19:00:15Z

Add section "Github View Code at this Point".

← Older revision		Revision as of 16:35, 26 February 2026
Line 281:		Line 281:

	(2) Branch creation on individual commits to overcome unwanted squashes during interactive rebasing.		(2) Branch creation on individual commits to overcome unwanted squashes during interactive rebasing.
		+
		+	=== [[#top\|^]] branch maintenance ===
		+
		+	Over time git branches tend to accumulate both in local repos and shared code repositories. A branch may be deleted on a shared repository but will persist in git meta-data in a local repository. For those who enjoy command and argument "tab completion" this can be troublesome. A locally deleted branch still "shows up" in tab completions when the branch existed on the shared "origin" or remote repository. To overcome this issue the git command:
		+
		+	$ git remote prune origin
		+
		+	This also affects the reporting of `git log`. Those reports normally annotate those commits which are attached to a branch, both local branches and remote branches. The remote associations in a local git log are not automatically updated when remote branches are deleted. The `git remote prune origin` command effects this update, so that `git log` output no longer shows branches which have been deleted on the remote or origin repository.
		+
		+	NOTE: this command is duplicated in a later section. That duplicate should be removed.

	<!-- comentario -->		<!-- comentario -->

← Older revision		Revision as of 22:01, 28 January 2026
Line 209:		Line 209:

	== Commit Signing ==		== Commit Signing ==
		+
		+	Some but not all steps to create and use GPG signing key:
		+
		+	# Be sure to inform local git client of GPG key with:
		+	# (1) gpg --list-secret-keys --keyid-format=long
		+	# (2) git config --global user.signingkey [key_id_long_format]
		+	# (3) export GPG_TTY=$(tty)

	To allow for GPG signing over ssh sessions, on the physically remote host:		To allow for GPG signing over ssh sessions, on the physically remote host:

← Older revision		Revision as of 06:23, 24 January 2026
Line 213:		Line 213:

	$ export GPG_TTY=$(tty)		$ export GPG_TTY=$(tty)
		+
		+	There may be more steps, see
		+	https://superuser.com/questions/520980/how-to-force-gpg-to-use-console-mode-pinentry-to-prompt-for-passwords.

	== [[#top\|^]] Git grep ==		== [[#top\|^]] Git grep ==

← Older revision		Revision as of 06:21, 24 January 2026
Line 207:		Line 207:

	<!-- odne komentar -->		<!-- odne komentar -->
		+
		+	== Commit Signing ==
		+
		+	To allow for GPG signing over ssh sessions, on the physically remote host:
		+
		+	$ export GPG_TTY=$(tty)

	== [[#top\|^]] Git grep ==		== [[#top\|^]] Git grep ==

@@ Line 541: / Line 541: @@
 <!-- odne komentar -->
-== [[#top|^]] Git log related ==
+== [[#top|^]] Git log ==
 <i>Keywords:  git log pickaxe option</i>
@@ Line 551: / Line 551: @@
 Ways to invoke `git log`:
 *  https://opensource.com/article/21/4/git-whatchanged  `git log --raw`, `git log --patch` and `git whatchanged`.

← Older revision		Revision as of 00:09, 8 January 2026
Line 142:		Line 142:

	$ git rev-parse --show-toplevel		$ git rev-parse --show-toplevel
		+
		+	Some additional uses of git rev-parse here at link to Eduardo Silva Medium dot com article:
		+
		+	* https://medium.com/@eduardosilva_94960/git-tips-the-hidden-magic-of-git-rev-parse-for-git-enthusiasts-7462a0054023

	<!-- odne komentar -->		<!-- odne komentar -->

@@ Line 334: / Line 334: @@
 </ul>
-A good explanation of uses of `git rebase --onto commit1 commit2 [commit3]` by Enrico Campidoglio:
+A good explanation of uses of `git rebase --onto commit1 commit2 [commit3]` by Enrico Campidogli0:
 <ul>
 *  https://stackoverflow.com/questions/29914052/how-to-git-rebase-a-branch-with-the-onto-command
 </ul>
 <!-- git rebase --onto Stackoverflow answer by Enrico Campidoglio.  Answer noted here in case Stackoverflow site ever becomes not available:

@@ Line 574: / Line 574: @@
 == [[#top|^]] Git remotes ==
 Working with multiple git remotes , remote repositories.  The following tutorial link to Jigarius leads to a good article.  In attempting to set up a local git remote 'definition' with two remote URLs, it became clear that there are issues that break this effort when one remote repo is already created and has pre-existing history.  It doesn't matter how short or simple that history is.  So this is a good link, but may not be practical to set up multiple remotes to be updated with a single 'push' command when the remotes are not all fully under a given developer's control:
 *  https://jigarius.com/blog/multiple-git-remote-repositories

@@ Line 510: / Line 510: @@
 $ git stash list --all                         # . . . list stash entries for all branches of present local repository
 </pre>
 "Use of Git stash should be the exception and not the rule." - Cameron McKenzie, Editor In Chief, TechTarget

← Older revision		Revision as of 19:00, 8 July 2025
Line 559:		Line 559:

	<!-- comentario -->		<!-- comentario -->
		+
		+	== Github View Code at this Point ==
		+
		+	Example URL which shows code at a given commit:
		+
		+	https://github.com/zephyrproject-rtos/zephyr/blob/91f8c1aea9849895245299b40bee06d92404f3df/samples/subsys/fs/littlefs/src/main.c
		+
		+	<!-- odne komentar -->

	== [[#top\|^]] Git remotes ==		== [[#top\|^]] Git remotes ==