Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>One way of doing this is the inverse - remove everything but the file you want to keep.</p> <p>Basically, <strong>make a copy</strong> of the repository, then use <a href="http://git-scm.com/docs/git-filter-branch" rel="noreferrer"><code>git filter-branch</code></a> to remove everything but the file/folders you want to keep.</p> <p>For example, I have a project from which I wish to extract the file <code>tvnamer.py</code> to a new repository:</p> <pre><code>git filter-branch --tree-filter 'for f in *; do if [ $f != "tvnamer.py" ]; then rm -rf $f; fi; done' HEAD </code></pre> <p>That uses <code>git filter-branch --tree-filter</code> to go through each commit, run the command and recommit the resulting directories content. This is extremely destructive (so you should only do this on a copy of your repository!), and can take a while (about 1 minute on a repository with 300 commits and about 20 files)</p> <p>The above command just runs the following shell-script on each revision, which you'd have to modify of course (to make it exclude your sub-directory instead of <code>tvnamer.py</code>):</p> <pre><code>for f in *; do if [ $f != "tvnamer.py" ]; then rm -rf $f; fi; done </code></pre> <p>The biggest obvious problem is it leaves all commit messages, even if they are unrelated to the remaining file. The script <a href="http://github.com/jwiegley/git-scripts/blob/master/git-remove-empty-commits" rel="noreferrer">git-remove-empty-commits</a>, fixes this..</p> <pre><code>git filter-branch --commit-filter 'if [ z$1 = z`git rev-parse $3^{tree}` ]; then skip_commit "$@"; else git commit-tree "$@"; fi' </code></pre> <p>You need to use the <code>-f</code> force argument run <code>filter-branch</code> again with anything in <code>refs/original/</code> (which basically a backup)</p> <p>Of course this will never be perfect, for example if your commit messages mention other files, but it's about as close a git current allows (as far as I'm aware anyway).</p> <p><strong>Again, only ever run this on a copy of your repository!</strong> - but in summary, to remove all files but "thisismyfilename.txt":</p> <pre><code>git filter-branch --tree-filter 'for f in *; do if [ $f != "thisismyfilename.txt" ]; then rm -rf $f; fi; done' HEAD git filter-branch -f --commit-filter 'if [ z$1 = z`git rev-parse $3^{tree}` ]; then skip_commit "$@"; else git commit-tree "$@"; fi' </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POHow to extract a git subdirectory and make a submodule out of it?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USdbr
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. CO`git filter-branch` has (nowadays?) a built-in option to remove empty commits, namely `--prune-empty`. A better guide to `git filter-branch` is in the answers to this question: http://stackoverflow.com/questions/359424/detach-subdirectory-into-separate-git-repository
      singulars
      1. PO
      1. USBlaisorblade
 

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