Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

git-show-index(1) [linux man page]

GIT-SHOW-INDEX(1)						    Git Manual							 GIT-SHOW-INDEX(1)

NAME
git-show-index - Show packed archive index SYNOPSIS
git show-index < idx-file DESCRIPTION
Reads given idx file for packed Git archive created with git pack-objects command, and dumps its contents. The information it outputs is subset of what you can get from git verify-pack -v; this command only shows the packfile offset and SHA-1 of each object. GIT
Part of the git(1) suite Git 1.8.5.3 01/14/2014 GIT-SHOW-INDEX(1)

Check Out this Related Man Page

GIT-INDEX-PACK(1)						    Git Manual							 GIT-INDEX-PACK(1)

NAME
git-index-pack - Build pack index file for an existing packed archive SYNOPSIS
git index-pack [-v] [-o <index-file>] <pack-file> git index-pack --stdin [--fix-thin] [--keep] [-v] [-o <index-file>] [<pack-file>] DESCRIPTION
Reads a packed archive (.pack) from the specified file, and builds a pack index file (.idx) for it. The packed archive together with the pack index can then be placed in the objects/pack/ directory of a git repository. OPTIONS
-v Be verbose about what is going on, including progress status. -o <index-file> Write the generated pack index into the specified file. Without this option the name of pack index file is constructed from the name of packed archive file by replacing .pack with .idx (and the program fails if the name of packed archive does not end with .pack). --stdin When this flag is provided, the pack is read from stdin instead and a copy is then written to <pack-file>. If <pack-file> is not specified, the pack is written to objects/pack/ directory of the current git repository with a default name determined from the pack content. If <pack-file> is not specified consider using --keep to prevent a race condition between this process and git repack. --fix-thin Fix a "thin" pack produced by git pack-objects --thin (see git-pack-objects(1) for details) by adding the excluded objects the deltified objects are based on to the pack. This option only makes sense in conjunction with --stdin. --keep Before moving the index into its final destination create an empty .keep file for the associated pack file. This option is usually necessary with --stdin to prevent a simultaneous git repack process from deleting the newly constructed pack and index before refs can be updated to use objects contained in the pack. --keep=<msg> Like --keep create a .keep file before moving the index into its final destination, but rather than creating an empty file place <msg> followed by an LF into the .keep file. The <msg> message can later be searched for within all .keep files to locate any which have outlived their usefulness. --index-version=<version>[,<offset>] This is intended to be used by the test suite only. It allows to force the version for the generated pack index, and to force 64-bit index entries on objects located above the given offset. --strict Die, if the pack contains broken objects or links. NOTE
Once the index has been created, the list of object names is sorted and the SHA1 hash of that list is printed to stdout. If --stdin was also used then this is prefixed by either "pack ", or "keep " if a new .keep file was successfully created. This is useful to remove a .keep file used as a lock to prevent the race with git repack mentioned above. GIT
Part of the git(1) suite Git 1.7.10.4 11/24/2012 GIT-INDEX-PACK(1)
Man Page

12 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Featured Books and Articles by Active Forum Members

The UNIX and Linux Forums have a number of active members that have published books or papers related to shell programming and scripting. You can check out their publications here: Link Removed Please note, as you can imagine, our forum experts can be quite busy! You will get a response... (0 Replies)
Discussion started by: Neo
0 Replies

2. Emergency UNIX and Linux Support

User Guide: Posting in the Emergency Forum

Emergency UNIX and Linux Support !! Help Me! Forum (Request Urgent Help) README FIRST: How to Request Emergency or Urgent Help: You may post emergency work-related questions in the emergency forum. To post in this forum you will need to use your Bits. All questions answered on a "best... (0 Replies)
Discussion started by: Neo
0 Replies

3. Homework & Coursework Questions

Rules for Homework & Coursework Questions Forum

Homework Help: On Posting Questions: Any and all high school and undergraduate homework assignments or textbook style exercises for which you are seeking assistance are to be posted only in our Homework & Coursework Questions area--not in blogs, visitor messages, PMs, or the main technical... (0 Replies)
Discussion started by: Neo
0 Replies

4. What is on Your Mind?

Please Donate to the Red Cross for Earthquake and Tsunami Relief in Japan

Dear Forum Members, The UNIX and Linux Forums are working directly with the Red Cross to provide ad banners on our site to support Earthquake and Tsunami Relief in Japan. Registered users do not see these banners. However, if you wish to contribute directly on behalf of yourself and the... (8 Replies)
Discussion started by: Neo
8 Replies

5. How to Post in the The UNIX and Linux Forums

Forum Video Tutorial: How to Use Code Tags

How to Use Code Tags in The UNIX and Linux Forums Developer: This video tutorial was created by scott for forum users. Everyone should use code tags when posting code and command line logic in the forums. cPF45jjWe7Q A full list of BB codes is available here. (8 Replies)
Discussion started by: Neo
8 Replies

6. What is on Your Mind?

Merry Christmas!

https://www.unix.com/members/neo-albums-forum-pics-picture567-merry-christmas.png (1 Reply)
Discussion started by: Neo
1 Replies

7. UNIX for Beginners Questions & Answers

Simple rules of the UNIX.COM forums:

RULES OF THE UNIX AND LINUX FORUMS For the latest version of the community rules (the official community rules page), please visit here. No flames, shouting (all caps), sarcasm, bullying, profanity or arrogant posts. No negative comments about others or impolite remarks. Be patient. No... (1 Reply)
Discussion started by: Neo
1 Replies

8. Shell Programming and Scripting

Scripts without shebang

I see lot of ad-hoc shell scripts in our servers which don't have a shebang at the beginning . Does this mean that it will run on any shell ? Is it a good practice to create scripts (even ad-hoc ones) without shebang ? (16 Replies)
Discussion started by: kraljic
16 Replies

9. What is on Your Mind?

Status of UNIX.COM Forum Transformation

Having spent a lot of time over the past year taking a legacy vBulletin site (this forum) and making the site responsive on mobile; I've happy with the results; but it will soon be time to move on. Basically, at our core, we are a LAMP (Linux, Apache2, MySQL and PHP) site, and vBulletin was... (6 Replies)
Discussion started by: Neo
6 Replies

10. What is on Your Mind?

Answers to Recently Asked Questions about UNIX.COM

Here are some answers to some of the recent questions I have received about UNIX.COM. So, I thought I would take time to answer them here in this post: Is it expected that the original poster "thank" everyone who responds to his / her discussion thread? It is always a good practice in all... (7 Replies)
Discussion started by: Neo
7 Replies

11. What is on Your Mind?

YouTube: How to Use Code Tags and Format Posts @UNIX.com

By special request, and long overdue, I have updated our "code tags" video and so now we have: How to Use Code Tags and Format Posts @UNIX.com in 4K https://youtu.be/4BuPvWJV__k (3 Replies)
Discussion started by: Neo
3 Replies

12. What is on Your Mind?

UNIX.com End of Year (EOY) Report (2019)

Here is a quick EOY report for 2019. 2019 has been a year of "downward trend reversal" for UNIX.com. In fact, if we compare total Google search impressions from the peak days in December 2019 to the peak days in mid December 2018, traffic is up 43% percent. That is a very respectable growth... (0 Replies)
Discussion started by: Neo
0 Replies