GIT-GET-TAR-COMMI(1) Git Manual GIT-GET-TAR-COMMI(1)NAME
git-get-tar-commit-id - Extract commit ID from an archive created using git-archive
SYNOPSIS
git get-tar-commit-id
DESCRIPTION
Read a tar archive created by git archive from the standard input and extract the commit ID stored in it. It reads only the first 1024
bytes of input, thus its runtime is not influenced by the size of the tar archive very much.
If no commit ID is found, git get-tar-commit-id quietly exists with a return code of 1. This can happen if the archive had not been created
using git archive or if the first parameter of git archive had been a tree ID instead of a commit ID or tag.
GIT
Part of the git(1) suite
Git 2.17.1 10/05/2018 GIT-GET-TAR-COMMI(1)
Check Out this Related Man Page
GIT-TAR-TREE(1) Git Manual GIT-TAR-TREE(1)NAME
git-tar-tree - Create a tar archive of the files in the named tree object
SYNOPSIS
git tar-tree [--remote=<repo>] <tree-ish> [ <base> ]
DESCRIPTION
THIS COMMAND IS DEPRECATED. Use git archive with --format=tar option instead (and move the <base> argument to --prefix=base/).
Creates a tar archive containing the tree structure for the named tree. When <base> is specified it is added as a leading path to the files
in the generated tar archive.
git tar-tree behaves differently when given a tree ID versus when given a commit ID or tag ID. In the first case the current time is used
as modification time of each file in the archive. In the latter case the commit time as recorded in the referenced commit object is used
instead. Additionally the commit ID is stored in a global extended pax header. It can be extracted using git get-tar-commit-id.
OPTIONS
<tree-ish>
The tree or commit to produce tar archive for. If it is the object name of a commit object.
<base>
Leading path to the files in the resulting tar archive.
--remote=<repo>
Instead of making a tar archive from local repository, retrieve a tar archive from a remote repository.
CONFIGURATION
tar.umask
This variable can be used to restrict the permission bits of tar archive entries. The default is 0002, which turns off the world write
bit. The special value "user" indicates that the archiving user's umask will be used instead. See umask(2) for details.
EXAMPLES
git tar-tree HEAD junk | (cd /var/tmp/ && tar xf -)
Create a tar archive that contains the contents of the latest commit on the current branch, and extracts it in /var/tmp/junk directory.
git tar-tree v1.4.0 git-1.4.0 | gzip >git-1.4.0.tar.gz
Create a tarball for v1.4.0 release.
git tar-tree v1.4.0^{tree} git-1.4.0 | gzip >git-1.4.0.tar.gz
Create a tarball for v1.4.0 release, but without a global extended pax header.
git tar-tree --remote=example.com:git.git v1.4.0 >git-1.4.0.tar
Get a tarball v1.4.0 from example.com.
git tar-tree HEAD:Documentation/ git-docs > git-1.4.0-docs.tar
Put everything in the current head's Documentation/ directory into git-1.4.0-docs.tar, with the prefix git-docs/.
AUTHOR
Written by Rene Scharfe.
DOCUMENTATION
Documentation by David Greaves, Junio C Hamano and the git-list <git@vger.kernel.org[1]>.
GIT
Part of the git(1) suite
NOTES
1. git@vger.kernel.org
mailto:git@vger.kernel.org
Git 1.7.1 07/05/2010 GIT-TAR-TREE(1)
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)
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)
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)
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)