Found 39 matching messages (0.094 seconds). Page 1 of 2.
... 0 >> rerereunresolved = 0 >> packrefs = 1 > > git-gc uses a "safe" pruning ... .147.g867f. Any further ideas? $ git config -l core.repositoryformatversion=0 ... reused 6 (delta 0) $ git prune $ git branch * master $ du -s ...
git - Guido Ostkamp - May 8 2008 - 14:55
... = 0 >>> rerereunresolved = 0 >>> packrefs = 1 >> >> git-gc uses a "safe" pruning mode ... ideas? Possibly that object got packed? git-prune only removes loose objects. ... the objects referenced by a deleted branch will be removed from ...
git - Brandon Casey - May 8 2008 - 16:07
... probably be pruned immediately during the same git-gc run. > > Well, not necessarily. If you created a large branch yesterday and you > are deleting it today, then ... branch was created yesterday and then deleted today even if packing had never ...
git - Brandon Casey - May 9 2008 - 12:54
... There is only the > master branch left, and only one commit ... uses the space > former occupied by the branch. I'm using ... and branch creation git branch -D test git config gc.reflogexpire ... list: send the line "unsubscribe git" in the body of a ...
git - Jeff King - May 8 2008 - 16:51
... "alternates") but about races between gc and > push (or fetch). Before ... working directory to the same branch as some other working directory ... t point to a valid git repository, because such a symlink ... also be deleted by any instance of git gc that notices ...
git - Jeremy Maitin-Shepard - May 9 2008 - 20:07
... pruned immediately during the same git-gc run. Well, not necessarily ... created a large branch yesterday and you are deleting it today ... not be accessible by ordinary git commands for a while, > > before ... you shouldn't be running gc at all in the first ...
git - Nicolas Pitre - May 9 2008 - 12:12
... that the objects referenced by a deleted branch will be > >> removed from the ... is a good thing to deprecate gc --prune. but if that means ... if they're packed if one is always using 'git gc' as we ... list: send the line "unsubscribe git" in the body of a ...
git - Nicolas Pitre - May 8 2008 - 17:15
... wrote: > Possibly that object got packed? git-prune only removes loose objects. > ... assured that the objects referenced by a deleted branch will be > removed from the repository eventually as long as 'git gc --prune' is > run periodically. Ok. I ...
git - Guido Ostkamp - May 8 2008 - 16:52
... assured that the objects referenced by a deleted branch will be >> removed from the repository eventually as long as 'git gc --prune' is >> run periodically. > > ... from this list: send the line "unsubscribe git" in the body of a message to ...
git - Jeff King - May 8 2008 - 17:01
... 07:45:31PM +0200, Guido Ostkamp wrote: > [gc] > reflogExpire = 0 > reflogExpireUnreachable = 0 > rerereresolved = 0 > rerereunresolved = 0 > packrefs = 1 git-gc uses a "safe" pruning mode, ...
git - Jeff King - May 8 2008 - 14:39
... to the repository when running e.g. git gc. >>> For servers, you may never be ... . Here is a possible solution: >>> >>> Each git process creates a log file of ... specify whether the symlinks correspond to deleted repositories, or to repositories that have ...
git - Jeremy Maitin-Shepard - May 9 2008 - 21:51
... test -f "$e.pack" + then + git unpack-objects < "$e.pack" || { + echo >&2 ... for those users not manually running git-gc, this code path won't ...
git - Brandon Casey - May 8 2008 - 21:41
... think it is a good thing to deprecate gc --prune. but if that means >> that ... will >> never be pruned if they're packed if one is always using 'git gc' as we >> ... unsubscribe from this list: send the line "unsubscribe git" in the body of a message to ...
git - Brandon Casey - May 8 2008 - 17:23
... "$PACKDIR/old-pack-$name.pack" || > + git unpack-objects < "$PACKDIR/old-pack-$ ... those users not manually > running git-gc, this code path won' ... are enough > pack files for git-gc to add -A to ... list: send the line "unsubscribe git" in the body of a ...
git - Jeff King - May 9 2008 - 00:19
... t there an issue with the "git gc" triggering because there may be ... old refs should go to a .git/lost+found directory and be ... not be accessible by ordinary git commands for a while, before ... list: send the line "unsubscribe git" in the body of a ...
git - Geert Bosch - May 9 2008 - 11:00
... probably be pruned immediately during the same git-gc run. > Maybe unreferenced objects and old ... will not be accessible by ordinary git commands for a while, > before they are ... this list: send the line "unsubscribe git" in the body of a message to ...
git - Brandon Casey - May 9 2008 - 11:14
... repository when running e.g. git gc. >> For servers, you may ... is a possible solution: >> >> Each git process creates a log file ... that you should not prune/gc the repository "clone --shared" aka ... list: send the line "unsubscribe git" in the body of a ...
git - Junio C Hamano - May 9 2008 - 21:21
... the case then you shouldn't be running gc at all > in the first place. True. I ... store (aka "alternates") but about races between gc and push (or fetch). Before push (or ... from this list: send the line "unsubscribe git" in the body of a message to ...
git - Junio C Hamano - May 9 2008 - 18:33
... I think it is a good thing to deprecate gc --prune. but if that means > that ... will > never be pruned if they're packed if one is always using 'git gc' as we > ... unsubscribe from this list: send the line "unsubscribe git" in the body of a message to ...
git - Jeff King - May 8 2008 - 17:17
... the repository when running e.g. git gc. > For servers, you may ... is a possible solution: > > Each git process creates a log file of ... 2 weeks is good enough. Any Git process that has been running ... list: send the line "unsubscribe git" in the body of a ...
git - Shawn O. Pearce - May 9 2008 - 20:20
