git/list[1] front-page[2] threads[3] people[4] search[5] about
 

git svn with non-standard svn layout

From
FMFabian Molder <fm122@arcor.de>
Date
Oct 9, 2009, 22:24 UTC
Message-ID
<loom.20091010T001433-536@post.gmane.org>
Hello,
- want to use git inside an huge SVN project
 --> so git-svn could do the job ..
- I struggle with two things:
   A) - the SVN project has an non-standard layout
   B) - want to have (several) git's for just the (few) peaces I work on
for A)
======
- svn layout looks like this (simplified):
  - trunk  (not really used, all interesting work in branches)
  - branches
    - r1.2
     - development
     - integration
    - r1.3
     - development
     - integration
    ...
- inside development and integration is:
       - xapplication1
       - xapplication2
       - xapplication3
       ...
       - aa
        -bb
         -cc
          - zapplication1
          - zapplication2
          - zapplication3
          ...
- I created an simplified svn test (from scratch; import/repo/workdir) 
  via this bash-script:   http://pastebin.ca/1608231
for B)
======
- the svn repo is very huge, but I'm only interested in these dirs:
         xapplication2/
         aa/bb/cc/zapplication1
- my objectives: 
   - have several local git's, just the ones I need:
     --> xapplication2/.git
     --> aa/bb/cc/zapplication1/.git
I tried to use "git config svn-remote.svn.branches" to do this,
 please see in function "do_git_svn" in bash-script - but no success
any hints appreciated 

regards, Fabian

Next: Eric Wong
Message 1 of 4 in “git svn with non-standard svn layout”
  1. Fabian MolderOct 9, 2009
  2. Eric WongOct 11, 2009
  3. Fabian MolderOct 11, 2009
  4. Eric WongOct 14, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.