#196 remove all photo/pics and other binary files from the git repository, rewrite history, move binary files to the rsync repo

Open
opened 3 years ago by vimuser · 12 comments

(and force-push it)

and host the pre-rewrite git repo at libreboot-old

binary files such as JPG/PNG images would be moved to the rsync repository, with a symlink to it called /no-git/ on the root of the website. pages with images would then be re-written (in the entire git history) to point to that instead

the current git repository is huge, simply because of all those photo/pics that are in the git history. libreboot itself is tiny, without them.

this work will be non-trivial and will likely take a week to two weeks.

If approved by core management, i think we should do this.

(and force-push it) and host the pre-rewrite git repo at libreboot-old binary files such as JPG/PNG images would be moved to the rsync repository, with a symlink to it called /no-git/ on the root of the website. pages with images would then be re-written (in the entire git history) to point to that instead the current git repository is huge, simply because of all those photo/pics that are in the git history. libreboot itself is tiny, without them. this work will be non-trivial and will likely take a week to two weeks. If approved by core management, i think we should do this.
Leah Rowe commented 3 years ago
Owner

alternatively, host the images in a separate git repository

the pages on the site will still have images on them but those images will no longer be hosted in the main git repository

the live instance of the site would have a directory in it called /no-git/ which is a symlink to either a separate git repository containing the images, or an rsync repository containing the images

since rsync is harder to use for public (to submit images), then hosting the images in a separate git repo would probably be better

alternatively, host the images in a separate git repository the pages on the site will still have images on them but those images will no longer be hosted in the main git repository the live instance of the site would have a directory in it called /no-git/ which is a symlink to either a separate git repository containing the images, or an rsync repository containing the images since rsync is harder to use for public (to submit images), then hosting the images in a separate git repo would probably be better
Swift Geek commented 3 years ago
Collaborator

i vote for git not because it's easier/harder but because it would preserve history

i vote for git not because it's easier/harder but because it would preserve history
Leah Rowe commented 3 years ago
Owner

the current git repository, before rewriting git history, would be renamed libreboot-old.git

Then we would have:

  • libreboot.git (rewritten one) - text only. only text!
  • libreboot-images.git - separate repository for binary files (e.g. JPG/PNG images)
the current git repository, before rewriting git history, would be renamed libreboot-old.git Then we would have: - libreboot.git (rewritten one) - text only. only text! - libreboot-images.git - separate repository for binary files (e.g. JPG/PNG images)
Leah Rowe commented 3 years ago
Owner

yes ok, forget rsync. separate git repo it is.

alyssa, andrew, paul, what are your thoughts?

if approved, i'll work on this (or delegate it to one of you if you want to. alyssa is good at this sort of thing for instance)

yes ok, forget rsync. separate git repo it is. alyssa, andrew, paul, what are your thoughts? if approved, i'll work on this (or delegate it to one of you if you want to. alyssa is good at this sort of thing for instance)
Andrew Robbins commented 3 years ago
Collaborator

Yeah, separate repo for the pics is fine with me.

Yeah, separate repo for the pics is fine with me.
Leah Rowe commented 3 years ago
Owner

now we just need paul and alyssa's thoughts on the issue

now we just need paul and alyssa's thoughts on the issue
Leah Rowe commented 3 years ago
Owner

alyssa told me privately that she'll work on it when she can.

so it looks like alyssa will be working on this.

i'm pretty sure paul will be OK with this but let's wait for his thoughts

alyssa told me privately that she'll work on it when she can. so it looks like alyssa will be working on this. i'm pretty sure paul will be OK with this but let's wait for his thoughts
Paul Kocialkowski commented 3 years ago
Collaborator

I'm in a favour of a separate git repo, but I think it would make more sense to have all the docs there, not only the binaries.

Also, I'd strongly be in favour of not rewriting the git history but just moving things out of it.

I'm in a favour of a separate git repo, but I think it would make more sense to have all the docs there, not only the binaries. Also, I'd strongly be in favour of not rewriting the git history but just moving things out of it.
Leah Rowe commented 3 years ago
Owner

paul, the current git repo will be backed up to libreboot-old.git

the rewritten repo which is text-only will become the main one. binaries (jpg/png images etc) will be moved to libreboot-images.git

alyssa, can you start working on this then?

paul, the current git repo will be backed up to libreboot-old.git the rewritten repo which is text-only will become the main one. binaries (jpg/png images etc) will be moved to libreboot-images.git alyssa, can you start working on this then?
Paul Kocialkowski commented 3 years ago
Collaborator

Why are you even asking if you're not going to provide any feedback on my answer and act as if I had agreed with the proposal?

Can't we get a discussion going instead?

Why are you even asking if you're not going to provide any feedback on my answer and act as if I had agreed with the proposal? Can't we get a discussion going instead?
Swift Geek commented 3 years ago
Collaborator

Somebody convinced me that splitting docs and code has some additional benefits, like easier bisecting, more readable history for both docs and code

So i would be in favor of splitting docs (with pics) from build system and other code

Somebody convinced me that splitting docs and code has some additional benefits, like easier bisecting, more readable history for both docs and code So i would be in favor of splitting docs (with pics) from build system and other code
Andrew Robbins commented 3 years ago
Collaborator

Thinking about it, I agree with Paul and Swift Geek that having both docs and binaries in the same, separate, repo would make more sense than just splitting off the images.

Thinking about it, I agree with Paul and Swift Geek that having both docs and binaries in the same, separate, repo would make more sense than just splitting off the images.
Sign in to join this conversation.
Loading...
Cancel
Save
There is no content yet.