From: Knut Eldhuset <knut@3d-radar•com>
To: git@vger•kernel.org
Cc: Michael J Gruber <git@drmicha•warpmail.net>
Subject: Re: Different svn-id URLs in history
Date: Thu, 09 Oct 2008 08:16:29 +0200 [thread overview]
Message-ID: <48EDA1BD.6070209@3d-radar.com> (raw)
In-Reply-To: <48EC7022.7030707@drmicha.warpmail.net>
Michael J Gruber wrote:
> svn is typically "abused" in the sense that one svn repo is used for
> separate projects (your subtrees). git-svn can deal with non-standard
> repo layouts.
>
I've decided to give up on cloning the whole svn repo. Cloning just our
src folder is sufficient for now, and it does follow a sensible repo layout.
Maybe I'll get back to this if I manage to find a way of reproducing the
previously described behavior.
Regards,
Knut
prev parent reply other threads:[~2008-10-09 6:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-07 10:58 Different svn-id URLs in history Knut Eldhuset
2008-10-07 15:01 ` Michael J Gruber
2008-10-08 6:34 ` Knut Eldhuset
2008-10-08 8:32 ` Michael J Gruber
2008-10-08 9:20 ` Knut Eldhuset
2008-10-08 9:23 ` Knut Eldhuset
2008-10-09 14:20 ` Michael J Gruber
2008-10-10 8:56 ` Knut Eldhuset
2008-10-09 6:16 ` Knut Eldhuset [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48EDA1BD.6070209@3d-radar.com \
--to=knut@3d-radar$(echo .)com \
--cc=git@drmicha$(echo .)warpmail.net \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox