Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

git-verify-tag(1) [xfree86 man page]

GIT-VERIFY-TAG(1)						    Git Manual							 GIT-VERIFY-TAG(1)

NAME
git-verify-tag - Check the GPG signature of tags SYNOPSIS
git verify-tag [--format=<format>] <tag>... DESCRIPTION
Validates the gpg signature created by git tag. OPTIONS
--raw Print the raw gpg status output to standard error instead of the normal human-readable output. -v, --verbose Print the contents of the tag object before validating it. <tag>... SHA-1 identifiers of Git tag objects. GIT
Part of the git(1) suite Git 2.17.1 10/05/2018 GIT-VERIFY-TAG(1)

Check Out this Related Man Page

GIT-LOST-FOUND(1)						    Git Manual							 GIT-LOST-FOUND(1)

NAME
git-lost-found - Recover lost refs that luckily have not yet been pruned SYNOPSIS
git lost-found DESCRIPTION
NOTE: this command is deprecated. Use git-fsck(1) with the option --lost-found instead. Finds dangling commits and tags from the object database, and creates refs to them in the .git/lost-found/ directory. Commits and tags that dereference to commits are stored in .git/lost-found/commit, and other objects are stored in .git/lost-found/other. OUTPUT
Prints to standard output the object names and one-line descriptions of any commits or tags found. EXAMPLE
Suppose you run git tag -f and mistype the tag to overwrite. The ref to your tag is overwritten, but until you run git prune, the tag itself is still there. $ git lost-found [1ef2b196d909eed523d4f3c9bf54b78cdd6843c6] GIT 0.99.9c ... Also you can use gitk to browse how any tags found relate to each other. $ gitk $(cd .git/lost-found/commit && echo ??*) After making sure you know which the object is the tag you are looking for, you can reconnect it to your regular .git/refs hierarchy. $ git cat-file -t 1ef2b196 tag $ git cat-file tag 1ef2b196 object fa41bbce8e38c67a218415de6cfa510c7e50032a type commit tag v0.99.9c tagger Junio C Hamano <junkio@cox.net> 1131059594 -0800 GIT 0.99.9c This contains the following changes from the "master" branch, since ... $ git update-ref refs/tags/not-lost-anymore 1ef2b196 $ git rev-parse not-lost-anymore 1ef2b196d909eed523d4f3c9bf54b78cdd6843c6 GIT
Part of the git(1) suite Git 1.7.10.4 11/24/2012 GIT-LOST-FOUND(1)
Man Page

4 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

No xorg.conf or XF86Config

There is no xorg.conf file and no XF86Config file on a certain FreeBSD machine: # locate xorg.conf /usr/local/man/man5/xorg.conf.5.gz # locate XF86Config # Can someone let me know if that means that there is a bare bones set up possible only? xrandr works fine, but I am looking for ways to... (6 Replies)
Discussion started by: figaro
6 Replies

2. Shell Programming and Scripting

Can a script resize it's own mintty console?

I'm looking for finer granularity than the 20 ANSI escape sequence screen modes. What I'd like to do is have the terminal increase it's own height when I have to show the user a long menu. Platform is Cygwin 64 running over Win 7 Pro. Mike (4 Replies)
Discussion started by: Michael Stora
4 Replies

3. UNIX for Advanced & Expert Users

Shopt -s histappend

What is the point of this? Whenever I close my shell it appends to the history file without adding this. I have never seen it overwrite my history file. # When the shell exits, append to the history file instead of overwriting it shopt -s histappend (3 Replies)
Discussion started by: cokedude
3 Replies

4. Fedora

Fedora 30 and Slackware 14.2, how to obtain the same rendering?

Look this very good rendering on Slackware 14.2 in my opinion is near perfect. https://i.stack.imgur.com/q5trL.png Now look the same page on Fedora 30 https://i.stack.imgur.com/FBQv7.png In my opinion the fonts on Fedora are too small and difficult to read, I prefer the fat fonts of... (20 Replies)
Discussion started by: Linusolaradm1
20 Replies