From: Mike Doherty <doherty@pythian.com>
To: git@vger.kernel.org
Subject: git-svn 1.7.0.4 doesn't report that a directory isn't under version control
Date: Wed, 25 Apr 2012 15:17:38 -0400 [thread overview]
Message-ID: <4F984DD2.2030804@pythian.com> (raw)
Hello,
I noticed today that git-svn doesn't handle the case where a directory
isn't under version control in subversion, but you're still within your
git tree:
doherty@mdd:~/code/libs_shared/t (my-py-2523)$ git svn info
Use of uninitialized value $lc_author in concatenation (.) or string at
/usr/lib/git-core/git-svn line 1135.
Use of uninitialized value $lc_rev in concatenation (.) or string at
/usr/lib/git-core/git-svn line 1136.
Path: .
URL: svn://svn..../libs_shared/branches/PY-2523/t
Repository Root: svn://svn....
Repository UUID: ...
Revision: 8045
Node Kind: directory
Schedule: normal
Last Changed Author:
Last Changed Rev:
Last Changed Date: 2012-04-25 15:10:51 -0400 (Wed, 25 Apr 2012)
doherty@mdd:~/code/libs_shared/t (my-py-2523)$ svn ls
svn://svn.pythian.com/pythian/procter/dispatcher_repo/libs_shared/branches/PY-2523/t
svn: URL 'svn://svn..../libs_shared/branches/PY-2523/t' non-existent in
that revision
doherty@mdd:~/code/libs_shared/t (my-py-2523)$ svn ls
svn://svn..../libs_shared/branches/PY-2523
Class/
Data/
README
Util.pm
VERSION
XML/
doherty@mdd:~/code/libs_shared/t (my-py-2523)$ git --version
git version 1.7.0.4
I expected git to report that the directory (t) was not under version
control, as svn did.
Thanks,
-Mike Doherty
--
--
Attending Collaborate12 Apr 22-26? Catch Pythian’s stellar roster of
speakers presenting on a wide array of hot Oracle technology topics. More
at pythian.com/news
reply other threads:[~2012-04-25 19:23 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=4F984DD2.2030804@pythian.com \
--to=doherty@pythian.com \
--cc=doherty@cs.dal.ca \
--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).