Note that there are some explanatory texts on larger screens.

plurals
  1. POHow to run svn update in a loop to import commits to git?
    text
    copied!<p><strong>Current setup</strong><br> I am running a local <em>git</em> repository in parallel to a <em>svn</em> checkout in the same folder. Whenever something new happens on the <em>svn</em> server I run <code>svn update</code> to download the commits. Then I <code>git add &amp;&amp; git commit</code> the whole set of changes to the <em>git</em> repository.</p> <p><strong>Task</strong><br> I want to checkout each commit separately to being able to <code>git add &amp;&amp; git commit</code> the change with the corresponding commit message from <em>svn</em>.</p> <p><strong>Ideas</strong><br> I already found out that I can use <code>svnversion</code> to retrieve the revision numbers of the working copy and the server.</p> <pre><code>// svnversion -h usage: svnversion [OPTIONS] [WC_PATH [TRAIL_URL]] Produce a compact 'version number' for the working copy path WC_PATH. TRAIL_URL is the trailing portion of the URL used to determine if WC_PATH itself is switched (detection of switches within WC_PATH does not rely on TRAIL_URL). The version number is written to standard output. For example: $ svnversion . /repos/svn/trunk 4168 The version number will be a single number if the working copy is single revision, unmodified, not switched and with an URL that matches the TRAIL_URL argument. If the working copy is unusual the version number will be more complex: 4123:4168 mixed revision working copy 4168M modified working copy 4123S switched working copy 4123P partial working copy, from a sparse checkout 4123:4168MS mixed revision, modified, switched working copy ... </code></pre> <p><strong>Note</strong><br> I would be happy to discuss ideas with you to solve the task.<br> A later setup would also include <em>svn externals</em> which is why I cannot checkout the <em>svn</em> repository via <em>git-svn</em>.</p>
 

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