StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
3921179
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
5
CommunityOwnedDate
CreationDate
2010-10-13T06:09:38.777
FavoriteCount
0
LastActivityDate
2015-04-19T09:56:36.930
LastEditDate
2017-05-23T12:00:40.917
LastEditorUserId
-1
OwnerUserId
6309
ParentId
3921153
PostTypeId
2
Score
97
ViewCount
0
LastEditorDisplayName
text
Body
You can try: <ul> <li><code>"git mv -f foo.txt Foo.txt"</code> (note: this is <a href="https://stackoverflow.com/a/24979063/6309">no longer needed since git 2.0.1</a>) </li> <li>to set <code>ignorecase</code> to false in the config file.</li> </ul> <hr> But the issue of case (on Windows for instance) is described in the <a href="http://code.google.com/p/msysgit/issues/detail?id=228" rel="nofollow noreferrer">msysgit issue 228</a> (again: this should <a href="https://stackoverflow.com/a/24979063/6309">now -- June 2014 -- work with git 2.0.1</a>) <blockquote> there is always an option to set <code>ignorecase</code> to false in the config file that will force Unix like Git semantics on top of NTFS. Git supports this behavior but it is not the default - from NTFS point of view <code>a.txt</code> and <code>A.txt</code> are the same thing - so Git tries to preserve that as most users would expect </blockquote> <blockquote> As a better workaround, you can <pre><code>git mv foo.txt foo.txt.tmp && git mv foo.txt.tmp Foo.txt </code></pre> , which also changes the case of the file as stored on disk. </blockquote> This blog post <a href="http://www.paperplanes.de/2008/9/24/git_bits_renaming_with_lowercase.html" rel="nofollow noreferrer">illustrates the same issue on MacOs</a> during a rebase: <blockquote> The default on Mac OS X file systems is that they are case-insensitive. <code>FFFFFF.gif</code> is the same as <code>ffffff.gif</code>. If you delete the file in question, just from the file system, not from the Git index, mind you, you can merge the branch in question, and have it restore the file as if nothing happened. The steps are pretty simple: <pre><code>$ rm file/in/question.gif $ git merge trunk </code></pre> </blockquote> <hr> Anyhow, <a href="https://stackoverflow.com/questions/1094269/whats-the-purpose-of-git-mv">remember what git mv stands for</a>: <pre><code>mv oldname newname git add newname git rm oldname </code></pre> , so if <code>newname</code> and <code>oldname</code> clash, you need to make them different (even if it is only for a short period of time), hence the <code>git mv foo.txt foo.txt.tmp && git mv foo.txt.tmp Foo.txt</code>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POGit: File Rename
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCommunity
UserOwnerUserId
1. USVonC
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POGit: File Rename
 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
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId

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.