Managing nested structure

[daniel...@integral-it.ch]

Hello all,

In our Project, we have roughly the following structure:
- Proj A\Branches
  Development
  -- FolderX
  Main
- Proj B\Branches
  Development
  -- FolderY
  Main

The two projects A and B have different versioning, therefore they have different "Branches" folders. For our current development, though, we use one solution that is spread over all the files, so locally I need a structure like

MySolution.sln
FolderX
FolderY

At the moment it is done by having TFS set up with different working folder mappings within the workspace.

What is the best way for setting up our GIT repository locally under those circumstances.

One additional info: we map FolderX and FolderY, so as to avoid "Development" or "Main" in the folder path.

Yours Dany

[Matt Burke]

I think I see what you're doing. git-tfs doesn't have a good solution
for this right now. I'd like it to be able to support more complex
mappings [1], but there isn't a way to do that right now.

For now, you might be able to create separate git-tfs clones, and use
submodules to include them all in a main git repo.

[1] https://github.com/git-tfs/git-tfs/issues/229

> --
> You received this message because you are subscribed to the Google Groups
> "git-tfs-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to git-tfs-dev...@googlegroups.com.
> To post to this group, send email to git-t...@googlegroups.com.
> Visit this group at http://groups.google.com/group/git-tfs-dev?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>