git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Albert Krawczyk" <pro-logic@optusnet.com.au>
To: unlisted-recipients:; (no To-header on input)
Cc: <git@vger.kernel.org>
Subject: RE: Git SVN non-standard branch/tag/trunk layout
Date: Mon, 13 Dec 2010 11:55:30 +1100	[thread overview]
Message-ID: <000401cb9a60$71bcd610$55368230$@optusnet.com.au> (raw)
In-Reply-To: <m2fwu2ecy8.fsf@igel.home>

Andreas Schwab [mailto:schwab@linux-m68k.org]

> If they are multiple projects then you'll probably be better off 
> importing each project into its own git repository.
> 
> Andreas.

Yes, this is probably the 'better' way of dealing with it, and it works
fine. I was however wondering if there was a way to track the root of the
SVN directory with the structure I supplied earlier while maintaining a
'nice' structure in Git without having /trunk/, /branch/, /tag/
subdirectories appearing directly in the repository as standard folders. My
(extremely limited) understanding is that I would need to edit the config
file, specifically the fetch, branches and tags section of svn-remote. But I
am unsure of how this modified section would look like. 

Albert

  reply	other threads:[~2010-12-13  0:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-12 21:35 Git SVN non-standard branch/tag/trunk layout Albert Krawczyk
2010-12-13  0:25 ` Andreas Schwab
2010-12-13  0:55   ` Albert Krawczyk [this message]
2010-12-13 14:23 ` Stephen Bash
2010-12-13 21:08   ` Albert Krawczyk
2010-12-13 21:23     ` Stephen Bash

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='000401cb9a60$71bcd610$55368230$@optusnet.com.au' \
    --to=pro-logic@optusnet.com.au \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).