StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
3369796
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-07-30T08:28:05.323
FavoriteCount
0
LastActivityDate
2010-07-30T08:28:05.323
LastEditDate
LastEditorUserId
0
OwnerUserId
289908
ParentId
3367254
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
I had to do something very similar once, wasn't pretty but it was manageable. What I ended up doing was: <pre><code>git format-patch <commitish> --stdout > patches-for-upstream.mbox $EDITOR patches-for-upstream.mbox </code></pre> Inside the editor, I looked at which bits were common and needed changed to make "git am" do what I wanted. That turned out to be three lines, per file committed in each commit: <ul> <li>the line starting with <code>diff --git a/path/to/file b/path/to/file</code></li> <li>the line starting with <code>--- a/path/to/file</code></li> <li>the line starting with <code>+++ b/path/to/file</code></li> </ul> What the editor needs to do at this point is to go through these kind of lines and make the changes that you know are necessary to have all the patches apply to the other Git repository. I did that in Vim, using three quickly typed macroes, YMMV. Something along the lines of: <ul> <li>go to next line starting with <code>diff --git a/</code></li> <li>go forward to that slash after the <code>a</code></li> <li>change the path as you need it to be</li> <li>go forward to the slash after the <code>b/</code> (forward to next space from the <code>a</code> file, then <code>/</code>)</li> <li>change the path in the same way as a</li> <li>next line (the <code>---</code>)</li> <li>go forward to <code>a/</code></li> <li>change the path</li> <li>next line (the <code>+++</code>)</li> <li>go forward to <code>b/</code></li> <li>change the path</li> </ul> Repeat until the file's done. In Vim it was a matter of getting it in a macro once (<code>qq<long string of commands>q</code>), trying it out once (<code>@q</code>) and then doing it for the whole file (<code>999@q</code>). Save the file, go in the other Git repo, and try to <code>git am</code> it.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow can I modify the file path in a set of Git patches?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USmfontani
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
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
 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.