git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael J Gruber <git@drmicha.warpmail.net>
To: Knut Eldhuset <knut@3d-radar.com>
Cc: git@vger.kernel.org
Subject: Re: Different svn-id URLs in history
Date: Tue, 07 Oct 2008 17:01:44 +0200	[thread overview]
Message-ID: <48EB79D8.6090908@drmicha.warpmail.net> (raw)
In-Reply-To: <48EB40E1.40506@3d-radar.com>

Knut Eldhuset venit, vidit, dixit 07.10.2008 12:58:
> Hi,
> 
> After cloning my svn repository, I notice that the svn-id URL is 
> different when going back in history:
> 
> git-svn-id: https://server/trunk@300
> 
> vs
> 
> git-svn-id: https://server/trunk/some_folder/project/src@250
> 
> If i checkout the first version, I get a working copy that has the 
> folder "some_folder" in it. If I checkout the latter version, I get a 
> working copy with the contents of the folder "src". Why is this? I 
> thought I always was supposed to get a wc with the whole tree.
> 
> Regards,
> Knut Eldhuset

I take this is as an invitation for guesswork (given the amount of
details)...

You probably have commits which don't follow your usual svn repo layout
(trunk/some_folder/project/src) but commit to trunk/ directly. The output of

svn log -v -r300 https://server/trunk@300
svn log -v -r250 https://server/trunk/some_folder/project/src@250

should give some clues.

Michael

  reply	other threads:[~2008-10-07 15:03 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 [this message]
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

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=48EB79D8.6090908@drmicha.warpmail.net \
    --to=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.org \
    --cc=knut@3d-radar.com \
    /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.
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 NNTP newsgroup(s).