git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tyson Whitehead <twhitehead@gmail.com>
To: git@vger.kernel.org
Subject: revision range required for git-svn problem with 1.7.3.1
Date: Tue, 19 Oct 2010 17:05:33 -0400	[thread overview]
Message-ID: <201010191705.51978.twhitehead@gmail.com> (raw)

[-- Attachment #1: Type: Text/Plain, Size: 1240 bytes --]

I asked about this on the IRC channel the other day and was advised to submit 
a bug report to the mailing list.  My problem is this with our internal repo

$ svn co svn+ssh://svn@devel.sharcnet.ca/data/svn/sharcware

works as you would expect

$ git svn clone svn+ssh://svn@devel.sharcnet.ca/data/svn/sharcware
Initialized empty Git repository in .git/

checks out nothing.  However, if I do

$ svn log svn+ssh://svn@devel.sharcnet.ca/data/svn/sharcware -r HEAD
------------------------------------------------------------------------
r1576 | network | 2010-10-19 13:39:29 -0400 (Tue, 19 Oct 2010) | 1 line

Automated network config update.
------------------------------------------------------------------------

$ git svn clone svn+ssh://svn@devel.sharcnet.ca/data/svn/sharcware -r 1:r1576
...<whole bunch of cloning output removed>...

then I get everything as I should.  I would then think this should also work

$ git svn clone svn+ssh://svn@devel.sharcnet.ca/data/svn/sharcware -r 1:HEAD
Initialized empty Git repository in .git/

but it does not.

Thanks!  -Tyson

PS:  The repo is not organized according to the standard format at all.  It is 
just a single trunk rooted at /data/svn/sharcware.


[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

                 reply	other threads:[~2010-10-19 21:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=201010191705.51978.twhitehead@gmail.com \
    --to=twhitehead@gmail.com \
    --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.
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).