From: Sam Vilain <sam@vilain.net>
To: git@vger.kernel.org, microschulz@web.de
Cc: Benoit Sigoure <tsuna@lrde.epita.fr>,
Eric Wong <normalperson@yhbt.net>,
"Shawn O. Pearce" <spearce@spearce.org>
Subject: Re: git-svn {show,create}-ignore chokes upon subdirs
Date: Wed, 28 May 2008 20:34:23 +1200 [thread overview]
Message-ID: <483D190F.4030101@vilain.net> (raw)
In-Reply-To: <20080527162002.GA21855@penelope.zusammrottung.local>
Nikolaus Schulz wrote:
> Hi,
>
> when importing subversion repositories into git, git-svn show-ignore and
> create-ignore choke when scanning project subdirectories. For example,
> with the sequence
>
> git-svn init -s http://svn.red-bean.com/repos/producingoss producingoss-git-svn
> cd producingoss-git-svn
> git-svn fetch
> git-svn create-ignore
>
> the last command prints this:
>
> HTTP Path Not Found: PROPFIND request failed on '/repos/producingoss/!svn/bc/1465/ca': '/repos/producingoss/!svn/bc/1465/ca' path not found at /home/nikolaus/nfs/nsbp/git/git/git-svn line 1897
>
> Revision 1465 is the latest subversion revision of the project. git-svn
> create-ignore stages a correct .gitignore in the top level directory, then
> aborts with the same error. I have tested this with two svn projects, the
> result is identical. Bisecting suggested that this is broken since commit
> 01bdab84e31763a98206c31cf99b9dc3cb221356.
It helps to include the breaking change's details in the message in
reports like this. Here it is:
From: Benoit Sigoure <tsuna@lrde.epita.fr>
Subject: git-svn: add a generic tree traversal to fetch SVN properties
* git-svn.perl (&traverse_ignore): Remove.
(&prop_walk): New.
(&cmd_show_ignore): Use prop_walk.
[ew: This will ease the implementation of the `create-ignore',
`propget', and `proplist' commands]
Signed-off-by: Benoit Sigoure <tsuna@lrde.epita.fr>
Acked-by: Eric Wong <normalperson@yhbt.net>
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
As a side note, "svn:mergeinfo" is rapidly becoming an 'interesting'
property and should probably be added to the list. However, I think it
probably needs to go somewhere like do_fetch; I'll follow-up separately
about that.
Sam.
next prev parent reply other threads:[~2008-05-28 8:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-27 16:20 git-svn {show,create}-ignore chokes upon subdirs Nikolaus Schulz
2008-05-27 8:46 ` [PATCH] git-svn fails in prop_walk if $self->{path} is not empty Gerrit Pape
2008-05-27 22:54 ` Nikolaus Schulz
2008-05-28 8:34 ` Sam Vilain [this message]
2008-05-28 9:16 ` git-svn {show,create}-ignore chokes upon subdirs Nikolaus Schulz
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=483D190F.4030101@vilain.net \
--to=sam@vilain.net \
--cc=git@vger.kernel.org \
--cc=microschulz@web.de \
--cc=normalperson@yhbt.net \
--cc=spearce@spearce.org \
--cc=tsuna@lrde.epita.fr \
/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).