StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POGit commit to common submodule (master branch)
primarykey
Id
3590400
data
AcceptedAnswerId
3592542
AnswerCount
6
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-08-28T10:32:31.650
FavoriteCount
33
LastActivityDate
2018-07-03T09:48:02.337
LastEditDate
2015-02-17T04:46:09.240
LastEditorUserId
3366929
OwnerUserId
167897
ParentId
0
PostTypeId
1
Score
49
ViewCount
21130
LastEditorDisplayName
text
Body
I've two or more projects (let's call them ProjectFoo and ProjectBar) having some common code that I put in a submodule. My understanding is that if I commit changes to a submodule from within ProjectFoo it'll be in a detached head that only all ProjectFoo clones can see: <pre><code>(master) $ cd ProjectFooBarCommoneSubmodule/ (master) $ git commit -am "Common code fix." (56f21fb0...) $ git push Everything up-to-date </code></pre> That's probably because the <code>master</code> branch hasn't changed. I could probably do something like <code>git checkout master && git merge Everything up-to-date</code> but that seem pretty ugly. May be a <code>git reset --hard master</code> would do the same but it seems even uglier. How to have a common code shared by project, updated from within those projects using it? In other words, committing to that submodule should update all various repositories (repositories, not just clones) that use this same submodule. ---- EDIT ---- Visibly my checked-out repository was messed up and broken. It should have worked right from the start like that (on ProjectFoo in this example): <pre><code>(master) $ cd ProjectFooBarCommoneSubmodule/ (master) $ git commit -am "Common code fix." (master) $ git push .... fbfdd71..0acce63 master -> master (master) $ cd .. (master) $ git add ProjectFooBarCommoneSubmodule (master) $ git commit -m "Submodule update." </code></pre> Then to get that change from on other projects, like ProjectBar: <pre><code>(master) $ cd ProjectFooBarCommoneSubmodule/ (master) $ git pull </code></pre> Would update to the latest common code. A <code>git checkout master</code> may be required if it's on a detached head.
Tags
<git><commit><git-submodules>
Title
Git commit to common submodule (master branch)
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USWernight
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
2. PL
 singulars
 LinkTypeLinkTypeId
 LTDuplicate
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POGit commit to common submodule (master branch)
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 POGit commit to common submodule (master branch)
 UserUserId
 USDavid
 VoteTypeVoteTypeId
 VTFavorite
3. VO
 singulars
 PostPostId
 POGit commit to common submodule (master branch)
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
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.