{"thread":{"id":"3120","subject":"Remove \"historical\" objects from repository to save place","startedAt":"2006-01-21T19:18:50Z","lastAt":"2006-01-21T23:27:50Z","messageCount":8,"participants":["Andrey Borzenkov","Junio C Hamano","Petr Baudis","Randal L. Schwartz"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"14989","messageId":"200601212218.51055.arvidjaar@mail.ru","threadId":"3120","inReplyTo":null,"subject":"Remove \"historical\" objects from repository to save place","fromName":"Andrey Borzenkov","fromEmail":"arvidjaar@mail.ru","sentAt":"2006-01-21T19:18:50Z","receivedAt":"2006-01-21T19:18:50Z","isPatch":false,"sender":{"key":"arvidjaar@mail.ru","avatar":null},"body":"-----BEGIN PGP SIGNED MESSAGE-----\nHash: SHA1\n\nIs it possible to conserve space by removing old versions? Let's say I am not \ninterested in kernel versions before 2.6.15 - is it possible to remove them \nfrom repository cloned from one of \"official\" ones (Linus or stable).\n\nDescription of git-prune suggests that it may be possible by removing tags \nfrom refs/tags; OTOH I may have commit chain that will prevent them. Also \nwon't those tags come back after git fetch --tags?\n\nTIA\n\n- -andrey\n-----BEGIN PGP SIGNATURE-----\nVersion: GnuPG v1.4.2 (GNU/Linux)\n\niD8DBQFD0okaR6LMutpd94wRAqEZAKC5VAkNMlL9TEmgELynIUf24Dd9oQCeOejQ\nMdmc4lFsYXBHqofjQhgEIlU=\n=2j5N\n-----END PGP SIGNATURE-----\n"},{"id":"14996","messageId":"7v1wz1mjy8.fsf@assigned-by-dhcp.cox.net","threadId":"3120","inReplyTo":"200601212218.51055.arvidjaar@mail.ru","subject":"Re: Remove \"historical\" objects from repository to save place","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2006-01-21T19:58:55Z","receivedAt":"2006-01-21T19:58:55Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Andrey Borzenkov writes:\n\n> Description of git-prune suggests that it may be possible by removing tags \n> from refs/tags\n\nIf the documentation suggests that, then it is misleading.\n\n> OTOH I may have commit chain that will prevent them.\n\nCorrect.\n\n> Also \n> won't those tags come back after git fetch --tags?\n\nCorrect.\n\nYou might be able to cauterize the history at a specific commit\nand then re-clone. I've talked about how in \"[QUESTION] about\n.git/info/grafts file\" thread yesterday, so I won't repeat that.\n"},{"id":"14998","messageId":"20060121200615.GM28365@pasky.or.cz","threadId":"3120","inReplyTo":"7v1wz1mjy8.fsf@assigned-by-dhcp.cox.net","subject":"Re: Remove \"historical\" objects from repository to save place","fromName":"Petr Baudis","fromEmail":"pasky@suse.cz","sentAt":"2006-01-21T20:06:15Z","receivedAt":"2006-01-21T20:06:15Z","isPatch":false,"sender":{"key":"pasky@ucw.cz","avatar":"https://avatars.githubusercontent.com/u/18439?v=4"},"body":"Dear diary, on Sat, Jan 21, 2006 at 08:58:55PM CET, I got a letter\nwhere Junio C Hamano said that...\n> You might be able to cauterize the history at a specific commit\n> and then re-clone. I've talked about how in \"[QUESTION] about\n> .git/info/grafts file\" thread yesterday, so I won't repeat that.\n\nShouldn't the git-prune be sufficient after cauterizing the history?\n\n-- \n\t\t\t\tPetr \"Pasky\" Baudis\nStuff: http://pasky.or.cz/\nOf the 3 great composers Mozart tells us what it's like to be human,\nBeethoven tells us what it's like to be Beethoven and Bach tells us\nwhat it's like to be the universe. -- Douglas Adams\n"},{"id":"15002","messageId":"7virsdl44q.fsf@assigned-by-dhcp.cox.net","threadId":"3120","inReplyTo":"20060121200615.GM28365@pasky.or.cz","subject":"Re: Remove \"historical\" objects from repository to save place","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2006-01-21T20:25:57Z","receivedAt":"2006-01-21T20:25:57Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Petr Baudis writes:\n\n>> You might be able to cauterize the history at a specific commit\n>> and then re-clone. I've talked about how in \"[QUESTION] about\n>> .git/info/grafts file\" thread yesterday, so I won't repeat that.\n>\n> Shouldn't the git-prune be sufficient after cauterizing the history?\n\nLogically yes, but practically no.\n\nMost likely what the original requestor cloned from Linus has\nbeen already packed so git-prune would not do much.\n"},{"id":"15004","messageId":"86slrhe270.fsf@blue.stonehenge.com","threadId":"3120","inReplyTo":"7virsdl44q.fsf@assigned-by-dhcp.cox.net","subject":"Re: Remove \"historical\" objects from repository to save place","fromName":"Randal L. Schwartz","fromEmail":"merlyn@stonehenge.com","sentAt":"2006-01-21T20:49:39Z","receivedAt":"2006-01-21T20:49:39Z","isPatch":false,"sender":{"key":"merlyn@stonehenge.com","avatar":"https://gravatar.com/avatar/dc528d210743ff0333e6213f9ee7b33b23f1b7bc1f3c5a8c2d819074ecd7ab19?d=mp&s=160"},"body":">>>>> \"Junio\" == Junio C Hamano writes:\n\nJunio> Most likely what the original requestor cloned from Linus has\nJunio> been already packed so git-prune would not do much.\n\nWait. Does that mean that:\n\n$ git-checkout -b playground\n$ work work work\n$ git-commit -m 'snapshot'\n$ git-checkout -b master\n$ git-repack -a -d\n\nmeans that even if I do\n\n$ git-branch -d playground\n$ git-repack -a -d\n\nI still have the commit from playground as objects inside my one big pack?\n\nIck. How do I make that go away?\n\n-- \nRandal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095\n \nPerl/Unix/security consulting, Technical writing, Comedy, etc. etc.\nSee PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!\n"},{"id":"15008","messageId":"7vbqy5l0er.fsf@assigned-by-dhcp.cox.net","threadId":"3120","inReplyTo":"86slrhe270.fsf@blue.stonehenge.com","subject":"Re: Remove \"historical\" objects from repository to save place","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2006-01-21T21:46:20Z","receivedAt":"2006-01-21T21:46:20Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"merlyn@stonehenge.com (Randal L. Schwartz) writes:\n\n>>>>>> \"Junio\" == Junio C Hamano writes:\n>\n> Junio> Most likely what the original requestor cloned from Linus has\n> Junio> been already packed so git-prune would not do much.\n>\n> Wait. Does that mean that:\n>\n> $ git-checkout -b playground\n> $ work work work\n> $ git-commit -m 'snapshot'\n> $ git-checkout -b master\n> $ git-repack -a -d\n>\n> means that even if I do\n>\n> $ git-branch -d playground\n> $ git-repack -a -d\n>\n> I still have the commit from playground as objects inside my one big pack?\n\nRepack retraces from all the available refs, so that is fine.\n\nPasky was talking about prune, which is a different animal.\n"},{"id":"15009","messageId":"200601220046.34151.arvidjaar@mail.ru","threadId":"3120","inReplyTo":"7v1wz1mjy8.fsf@assigned-by-dhcp.cox.net","subject":"Re: Remove \"historical\" objects from repository to save place","fromName":"Andrey Borzenkov","fromEmail":"arvidjaar@mail.ru","sentAt":"2006-01-21T21:46:32Z","receivedAt":"2006-01-21T21:46:32Z","isPatch":false,"sender":{"key":"arvidjaar@mail.ru","avatar":null},"body":"-----BEGIN PGP SIGNED MESSAGE-----\nHash: SHA1\n\nOn Saturday 21 January 2006 22:58, Junio C Hamano wrote:\n>\n> You might be able to cauterize the history at a specific commit\n> and then re-clone. I've talked about how in \"[QUESTION] about\n> ..git/info/grafts file\" thread yesterday, so I won't repeat that.\n\nthank you, quite complete description. One question - any caveats in using git \nls-remote to fetch graft point?\n\necho $(git ls-remote \ngit://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git v2.6.15 \n| cut -f1) > .git/info/grafts\n\netc\n\nthis avoids downloading over 1G in the first place.\n\nregards\n\n- -andrey\n-----BEGIN PGP SIGNATURE-----\nVersion: GnuPG v1.4.2 (GNU/Linux)\n\niD8DBQFD0qu6R6LMutpd94wRAtuzAJoCT15+8d9BcIEhOxmD9lrRGWE6EQCghg5l\nSR5g1+nAUNlltYyXydxsFAs=\n=U2cu\n-----END PGP SIGNATURE-----\n"},{"id":"15012","messageId":"200601220227.56367.arvidjaar@mail.ru","threadId":"3120","inReplyTo":"20060121200615.GM28365@pasky.or.cz","subject":"Re: Remove \"historical\" objects from repository to save place","fromName":"Andrey Borzenkov","fromEmail":"arvidjaar@mail.ru","sentAt":"2006-01-21T23:27:50Z","receivedAt":"2006-01-21T23:27:50Z","isPatch":false,"sender":{"key":"arvidjaar@mail.ru","avatar":null},"body":"-----BEGIN PGP SIGNED MESSAGE-----\nHash: SHA1\n\nOn Saturday 21 January 2006 23:06, Petr Baudis wrote:\n> Dear diary, on Sat, Jan 21, 2006 at 08:58:55PM CET, I got a letter\n> where Junio C Hamano said that...\n>\n> > You might be able to cauterize the history at a specific commit\n> > and then re-clone. I've talked about how in \"[QUESTION] about\n> > .git/info/grafts file\" thread yesterday, so I won't repeat that.\n>\n> Shouldn't the git-prune be sufficient after cauterizing the history?\n\nthis did not work for me, at least applied naively. May be, it is due to the \nway I setup repository - first I created local version from 2.6.15 tree and \nthen pulled in remote one.\n\nAnyway repacking and pruning resulted in over 500MB size reduction so its OK \nfor me so far. I'll probably try fetching cleanly later.\n\nthank you and best regards\n\n- -andrey\n-----BEGIN PGP SIGNATURE-----\nVersion: GnuPG v1.4.2 (GNU/Linux)\n\niD8DBQFD0sN8R6LMutpd94wRAt1WAKC18LjAl+MbyfmvSvvNQGUF/mlbIgCfcu6s\nnuZtYttRsd673Yqlq3aKr+A=\n=B6jN\n-----END PGP SIGNATURE-----\n"}]}