bibledit-development
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[be] [ bibledit-Feature Requests-1826127 ] prune git data


From: SourceForge.net
Subject: [be] [ bibledit-Feature Requests-1826127 ] prune git data
Date: Fri, 18 Apr 2008 09:46:41 -0700

Feature Requests item #1826127, was opened at 2007-11-05 17:32
Message generated for change (Settings changed) made by teus
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=658624&aid=1826127&group_id=111189

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
>Status: Pending
Resolution: None
Priority: 5
Private: No
Submitted By: Teus Benschop (teus)
Assigned to: Nobody/Anonymous (nobody)
Summary: prune git data

Initial Comment:
If the git repository becomes too bulky over time, look for methods to prune a 
lot of data out, leaving only the revisions we desire.


----------------------------------------------------------------------

Comment By: Teus Benschop (teus)
Date: 2008-03-15 19:43

Message:
Logged In: YES 
user_id=890881
Originator: YES

Schedule could be like once in 30 days or so.

----------------------------------------------------------------------

Comment By: Teus Benschop (teus)
Date: 2008-03-15 19:42

Message:
Logged In: YES 
user_id=890881
Originator: YES

There are "health" git commands available in the documentation.


Check health and remove cruft.

    $ git fsck (1)
    $ git count-objects (2)
    $ git repack (3)
    $ git gc (4)

       1.

          running without --full is usually cheap and assures the
repository health reasonably well.
       2.

          check how many loose objects there are and how much disk space
is wasted by not repacking.
       3.

          without -a repacks incrementally. repacking every 4-5MB of loose
objects accumulation may be a good rule of thumb.
       4.

          it is easier to use git gc than individual housekeeping commands
such as prune and repack. This runs repack -a -d.

Repack a small project into single pack.

    $ git repack -a -d (1)
    $ git prune

       1.

          pack all the objects reachable from the refs into one pack, then
remove the other packs.



----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=658624&aid=1826127&group_id=111189




reply via email to

[Prev in Thread] Current Thread [Next in Thread]