Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>If you want to track ALL the remote svn branches, then the solution is as simple as:</p> <pre><code>git svn fetch </code></pre> <p>This will fetch ALL the remote branches that have not been fetched yet. </p> <p>Extra tip: if you checked out only the trunk at first, and later you want to track ALL branches, then edit <code>.git/config</code> to look like this and re-run <code>git svn fetch</code>:</p> <pre><code>[svn-remote "svn"] url = https://svn/path_to_repo_root/ fetch = path_to_trunk:refs/remotes/git-svn branches = path_to_branches/*:refs/remotes/* </code></pre> <p>The key points are <code>url</code> should point to the repository root, and the paths defined in <code>fetch</code> and <code>branches</code> should be relative to <code>url</code>. </p> <p>If you want to fetch only specific branches instead of ALL, there is a nice example in <code>git svn --help</code>:</p> <pre><code>[svn-remote "huge-project"] url = http://server.org/svn fetch = trunk/src:refs/remotes/trunk branches = branches/{red,green}/src:refs/remotes/branches/* tags = tags/{1.0,2.0}/src:refs/remotes/tags/* </code></pre> <p>With older versions of <code>git-svn</code>, once you specified branches like this, you might not be able to get new branches with <code>git svn fetch</code>. One workaround is adding more <code>fetch</code> lines, like this:</p> <pre><code>[svn-remote "huge-project"] url = http://server.org/svn fetch = trunk/src:refs/remotes/trunk fetch = branches/blue:refs/remotes/branches/blue fetch = branches/yellow:refs/remotes/branches/yellow branches = branches/{red,green}/src:refs/remotes/branches/* </code></pre> <p>Another workaround by @AndyEstes: edit <code>.git/svn/.metadata</code> and change the value of <code>branches-maxRev</code> or <code>tags-maxRev</code> to a revision before any newly-specified branches or tags were created. Once you've done this, run <code>git svn fetch</code> to track the new svn remote branch.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow do I tell git-svn about a remote branch created after I fetched the repo?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USjanos
    1. USjanos
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI am also unable to change the branches line and need to use additional fetch lines.
      singulars
      1. PO
      1. USsandos
    2. COI like this solution better because, this one was able to show me nice graph in git also was able to see the history in files. With the accepted solution, it treated each branch with its own history and only showed the last commit (one that created the branch) and I was not able to see file change history. Only problem I have is not being able to add the branches later as you indicated.. I hope this get resolved soon.
      singulars
      1. PO
      1. USbond
    3. COIf you have already fetched the revision to which performed svn branching before you set those settings, you might want to do git svn reset.
      singulars
      1. PO
      1. USkcm1700
 

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.

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