GIT-PRUNE-PACKED(1) Git Manual GIT-PRUNE-PACKED(1)NAME
git-prune-packed - Remove extra objects that are already in pack files
SYNOPSIS
git prune-packed [-n|--dry-run] [-q|--quiet]
DESCRIPTION
This program searches the $GIT_OBJECT_DIRECTORY for all objects that currently exist in a pack file as well as the independent object
directories.
All such extra objects are removed.
A pack is a collection of objects, individually compressed, with delta compression applied, stored in a single file, with an associated
index file.
Packs are used to reduce the load on mirror systems, backup engines, disk storage, etc.
OPTIONS -n, --dry-run
Don't actually remove any objects, only show those that would have been removed.
-q, --quiet
Squelch the progress indicator.
SEE ALSO git-pack-objects(1)git-repack(1)GIT
Part of the git(1) suite
Git 1.8.5.3 01/14/2014 GIT-PRUNE-PACKED(1)
Check Out this Related Man Page
GIT-PRUNE(1) Git Manual GIT-PRUNE(1)NAME
git-prune - Prune all unreachable objects from the object database
SYNOPSIS
git prune [-n] [-v] [--expire <expire>] [--] [<head>...]
DESCRIPTION
Note
In most cases, users should run git gc, which calls git prune. See the section "NOTES", below.
This runs git fsck --unreachable using all the refs available in refs/, optionally with additional set of objects specified on the command
line, and prunes all unpacked objects unreachable from any of these head objects from the object database. In addition, it prunes the
unpacked objects that are also found in packs by running git prune-packed.
Note that unreachable, packed objects will remain. If this is not desired, see git-repack(1).
OPTIONS -n, --dry-run
Do not remove anything; just report what it would remove.
-v, --verbose
Report all removed objects.
--
Do not interpret any more arguments as options.
--expire <time>
Only expire loose objects older than <time>.
<head>...
In addition to objects reachable from any of our references, keep objects reachable from listed <head>s.
EXAMPLE
To prune objects not used by your repository nor another that borrows from your repository via its .git/objects/info/alternates:
$ git prune $(cd ../another && git rev-parse --all)
NOTES
In most cases, users will not need to call git prune directly, but should instead call git gc, which handles pruning along with many other
housekeeping tasks.
For a description of which objects are considered for pruning, see git fsck's --unreachable option.
SEE ALSO git-fsck(1), git-gc(1), git-reflog(1)GIT
Part of the git(1) suite
Git 1.8.5.3 01/14/2014 GIT-PRUNE(1)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)