StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
5775967
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
2011-04-25T06:48:18.810
CreationDate
2011-04-25T06:48:18.810
FavoriteCount
0
LastActivityDate
2011-04-25T06:48:18.810
LastEditDate
LastEditorUserId
0
OwnerUserId
139990
ParentId
1519154
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
almost forgot about this...sorry. as it turns out there is no easy solution to the problem that i described. i experimented with several options but each has drawbacks... nevertheless, maybe it is helpful if anybody else has the same problem: delete the unwanted file/folder from the git history <pre><code>git filter-branch --tree-filter "[ -f hugefile.bin ] && rm hugefile.bin" -f </code></pre> Pros: <ul> <li>effectively removes the file from your repository</li> </ul> Cons: <ul> <li>you will have to clean up your repository (get rid of the old commits as they are still in the git repo). either s.th. along <code>git gc --prune=now</code> or just clone your repository (will by default not clone your remote svn branch)</li> <li>the branch you get will not be synchronized with svn anymore (if you do another <code>git svn fetch</code> git will still fetch the unchanged history</li> </ul> <hr> cut of the history of svn when initially cloning <pre><code>git svn clone -r N http://yoursvnaddress myPartlyClonedRepo.git </code></pre> where N will be the earliest revision number that is synched Pros: <ul> <li>enables you to keep the size of your repository small (what I wanted in the first place)</li> </ul> Cons: <ul> <li>earlier history is "lost"</li> </ul> <hr> sparse checkout this has been a recent addition in git 1.7 and allows you to selectively modify your working directory <pre><code>git config core.sparsecheckout true echo "*" > .git/info/sparse-checkout echo '!path-to-huge-unwanted-dir/' >> .git/info/sparse-checkout git read-tree -m -u HEAD </code></pre> Pros <ul> <li>easy setup</li> </ul> Cons <ul> <li>does not affect the size of your database (.git)</li> </ul>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POremove data from a svn synchronized git repository
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USoliver
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POremove data from a svn synchronized git repository
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. This table or related slice is empty.

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.