From: wolf@wolfsden.cz
To: ruby-core@ruby-lang.org
Subject: [ruby-core:96644] [Ruby master Bug#16477] readline-ext repository is huge
Date: Fri, 03 Jan 2020 19:04:37 +0000 (UTC) [thread overview]
Message-ID: <redmine.issue-16477.20200103190437.ef612ff5938f67ad@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-16477.20200103190437@ruby-lang.org
Issue #16477 has been reported by graywolf (Gray Wolf).
----------------------------------------
Bug #16477: readline-ext repository is huge
https://bugs.ruby-lang.org/issues/16477
* Author: graywolf (Gray Wolf)
* Status: Open
* Priority: Normal
* Assignee:
* Target version:
* ruby -v: n/a
* Backport: 2.5: UNKNOWN, 2.6: UNKNOWN
----------------------------------------
Today I've cloned (my fresh new fork) of readline-ext
```
+ $ git clone git@github.com:graywolf/readline-ext.git
Cloning into 'readline-ext'...
remote: Enumerating objects: 3, done.
remote: Counting objects: 100% (3/3), done.
remote: Compressing objects: 100% (3/3), done.
remote: Total 389416 (delta 0), reused 1 (delta 0), pack-reused 389413
Receiving objects: 100% (389416/389416), 167.29 MiB | 2.83 MiB/s, done.
Resolving deltas: 100% (296077/296077), done.
```
~170 MB repository just for readline gem is way too huge. It is caused
by presence of following tags in the repository:
```
v1_0_r2
v1_8_7
v2_0_0_rc1
v2_1_0_rc1
v2_2_0_rc1
v2_7_0_preview1
v2_7_0_preview2
v2_7_0_preview3
v2_7_0_rc1
v2_7_0_rc2
```
Deleting them and running `git gc`
```
$ git tag --delete v1_0_r2 v1_8_7 v2_0_0_rc1 v2_1_0_rc1 v2_2_0_rc1 v2_7_0_preview1 v2_7_0_preview2 v2_7_0_preview3 v2_7_0_rc1 v2_7_0_rc2
Deleted tag 'v1_0_r2' (was 3db12e8b23)
Deleted tag 'v1_8_7' (was c36252fca2)
Deleted tag 'v2_0_0_rc1' (was ca6ccd436b)
Deleted tag 'v2_1_0_rc1' (was 9881a183bd)
Deleted tag 'v2_2_0_rc1' (was 050b43acce)
Deleted tag 'v2_7_0_preview1' (was c55db6aa27)
Deleted tag 'v2_7_0_preview2' (was 02aadf1032)
Deleted tag 'v2_7_0_preview3' (was b563439274)
Deleted tag 'v2_7_0_rc1' (was 8a40dce0ff)
Deleted tag 'v2_7_0_rc2' (was 75acbd5f00)
$ git gc --aggressive --prune=now
Enumerating objects: 1505, done.
Counting objects: 100% (1505/1505), done.
Delta compression using up to 4 threads
Compressing objects: 100% (1168/1168), done.
Writing objects: 100% (1505/1505), done.
Total 1505 (delta 584), reused 921 (delta 0)
Computing commit graph generation numbers: 100% (285/285), done.
$ du -sh .git
372K .git
```
gets the repo down to few hundred kilobytes. So imho you should really drop
those tags since there is no need to hold whole ruby source code in this
repository. Just something to consider.
--
https://bugs.ruby-lang.org/
next parent reply other threads:[~2020-01-03 19:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-16477.20200103190437@ruby-lang.org>
2020-01-03 19:04 ` wolf [this message]
2020-01-03 23:43 ` [ruby-core:96646] [Ruby master Bug#16477] readline-ext repository is huge eregontp
2020-01-05 2:27 ` [ruby-core:96670] " aycabta
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=redmine.issue-16477.20200103190437.ef612ff5938f67ad@ruby-lang.org \
--to=ruby-core@ruby-lang.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).