5 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi ,
I have replaced the cache batteries of my storageTek 2540 since yesterday at 7 PM and after charging the status of the batteries is today "Learning" .
I want to know if it's normal behavior ?
How can make to have OK status ?
Thanks for help
58ksh# sscs list -d ms_array -t Battery... (4 Replies)
Discussion started by: ghislino
4 Replies
2. Shell Programming and Scripting
Hi,
I will ftp aroung 80 files after connecting to an FTP Server. But after 2 minutes of connection, it is timed out and connection is dying. Server had a 2 minute connection timeout if connection is idle. But my question, Isn't tranfering files not considered as an activity. Is the connection... (7 Replies)
Discussion started by: vasuarjula
7 Replies
3. Post Here to Contact Site Administrators and Moderators
First of all, I want to thank everyone who runs this forum for the fine job they've done. While I myself have not yet had any need for help, I have enjoyed and learned while helping others.
Due diligence disclaimer: I searched for a discussion on this issue, using "tynt" and "copy paste", but... (11 Replies)
Discussion started by: alister
11 Replies
4. UNIX for Dummies Questions & Answers
I am using SunOS 5.7
I have installed Python 2.5 via make install
Without going into details, I'd like to uninstall it and replace it with an earlier version. Maybe as far back as 2.2.3. Unfortuantely, make uninstall gives me Don't know how to make target 'uninstall'. This is thematically... (2 Replies)
Discussion started by: Dbecker
2 Replies
5. News, Links, Events and Announcements
Mods: Delete this if you think that this is not appropriate.
I found this rather amusing. If you go to www.unix.net now you will see the OpenGroup selling license plates that read "Live Free or Die/Unix/Unix is a trademark of the OpenGroup"
(http://www.unix.net/unix_plates.html)
I just... (12 Replies)
Discussion started by: auswipe
12 Replies
LEARN ABOUT XFREE86
git-index-pack
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.
--check-self-contained-and-connected
Die if the pack contains broken links. For internal use only.
--fsck-objects
Die if the pack contains broken objects. For internal use only.
--threads=<n>
Specifies the number of threads to spawn when resolving deltas. This requires that index-pack be compiled with pthreads otherwise this
option is ignored with a warning. This is meant to reduce packing time on multiprocessor machines. The required amount of memory for
the delta search window is however multiplied by the number of threads. Specifying 0 will cause Git to auto-detect the number of CPU's
and use maximum 3 threads.
--max-input-size=<size>
Die, if the pack is larger than <size>.
NOTE
Once the index has been created, the list of object names is sorted and the SHA-1 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 2.17.1 10/05/2018 GIT-INDEX-PACK(1)