Databases
StackOverflow2013
Postsdbo
POCompletely remove (old) git commits from history
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POCompletely remove (old) git commits from history
    primarykey
    data
    text
    <p>I'm starting a project using git where I'll be committing very large files, but only a few times a week. I've tried to use git as-is and it seems to store the entire file in each commit where it is changed. This will not work for this project, the repository would grow out of control. So, I want to reduce the size of the repository.</p> <p>My first thought was to "simply" remove all commits older than say two weeks, or only keep e.g. five commits in the history (this is probably better :)) I've googled and read a lot from The Git Community Book and I guess I'm gonna need to work with <code>git-rebase</code> or <code>git-filter-branch</code>. The thing is I just can't seem to get it to work. </p> <p>Just to illustrate; I have a history H with only one branch (The master branch)</p> <blockquote> <p>A --> B --> C --> D --> E</p> </blockquote> <p>I want to remove some previous commits to make my history look like</p> <blockquote> <p>C --> D --> E</p> </blockquote> <p>Commits A and B should be completely purged. I've tried <code>git-rebase</code> but it seems to merge commits together rather than actually removing old ones, maybe I don't fully understand how rebase works.. Another thought I had was to remove everything from .git/objects and then build a new commit using <code>git-hash-object -w</code>, <code>git-mktree</code> and <code>git-commit-tree</code>, I have not yet managed to push this "artificial" tree to the server though.</p> <p>I won't be working with any branches, so there's no need taking these into account. </p> <p>What I'm wondering is if anyone can give me concrete usages of <code>git-rebase</code> if that's what I'm supposed to use? Or some other tips, examples of what I can do.</p> <p>Cheers!</p> <p><br/> <strong>Edit:</strong></p> <p>The large files will not be the same large files all the time, and some files will be replaced by new files. I want these replaced files to be <strong>completely purged</strong> from the history.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USThinner
    1. USThinner
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTDuplicate
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POCompletely remove (old) git commits from history
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POCompletely remove (old) git commits from history
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POCompletely remove (old) git commits from history
      1. This table or related slice is empty.
      1. VTUpMod
    1. CODo the later commits (C onwards) still contain the big files, or are they already removed (`git rm`) before?
      singulars
      1. POCompletely remove (old) git commits from history
      1. USPaŭlo Ebermann
    2. COYour use of the word `merge` to describe `git-rebase` makes me think you don't really understand `git-rebase`. `git-rebase` will move commits and apply them on top of a different head or, if you pass `-i`, let you rewrite and "squash" commits, change order, execute commands, edit commit messages, etc. No merging is involved.
      singulars
      1. POCompletely remove (old) git commits from history
      1. USalternative
    3. COIs git the right tool for this job? If you only want to keep the last few snapshots, then doesn't that defeat the point? Why not just use a flat file store?
      singulars
      1. POCompletely remove (old) git commits from history
      1. USRobie Basak
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload