Note that there are some explanatory texts on larger screens.

plurals
  1. POHow can I modify the file path in a set of Git patches?
    primarykey
    data
    text
    <p>I'm working on a Git repo that's been pulled from an SVN repo using <code>git svn</code>. Many moons ago, the SVN repo was created from a source tarball of the original (upstream) project. The original project had a file structure like the following:</p> <pre><code>/ COPYING README src/ ...many source files... </code></pre> <p>However, when the SVN repo was created, the README files, etc., were stripped out, and the app was created with <code>src/</code> as the root, so the repo now just looks like:</p> <pre><code>/ ...many source files </code></pre> <p>I recently converted this SVN repo into a Git repo. The original project is also in a Git repo, and I'd like to start tracking upstream changes so I can easily see what custom changes have been made (and submit patches back to the original project, if applicable). I've found the commit in the upstream repo that our SVN repo was created from, so now I'd like to apply our changes to that commit (in a branch). I can easily create a set of patches using <code>git format-patch</code> and apply them to the cloned upstream repo...except that the file structures are different, so the patches don't point to the correct files anymore. Is there a way to apply the patches from <code>git format-patch</code> to the <code>src/</code> directory in the cloned repo? (Note that the Git patches also have the necessary info like the original author name, email, and date, which I'd also like to apply and not have to do by hand, i.e., by messing around with <code>GIT_AUTHOR_EMAIL</code>, etc.)</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
 

Querying!

 
Guidance

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