On Sat, Jul 26, 2008 at 03:51:56PM +0200, Lele Gaifax <[EMAIL PROTECTED]> wrote:
> It would be great if you could send a patch for this. I do not know
> git at all, so I would be blindly tweaking the code...
> 
> Another thing that could help me would be a testcase that triggers the
> bad behaviour.

Yes, you are right. Pigeon, could we have a testcase for this?

Here is what I tried:

-- snip --
~/scm/darcs/tailor/test-scripts$ cat ./test-darcs2git-remove.sh
#!/bin/sh

# needs: test-darcs2git.include
#
# Test for converting from Darcs to Git.

. ./test-darcs2git.include
darcs_setup

echo "foo" > foo
darcs add foo
darcs record -v -a -A Nobody -m "add foo"

rm foo
darcs record -v -a -A Nobody -m "remove foo"

echo "foo" > foo
darcs add foo
darcs record -v -a -A Nobody -m "add foo again"

rm foo
darcs record -v -a -A Nobody -m "remove foo again"

testing_runs
-- snap --

But this does not trigger your problem.

In other words, the .git directory does not contain the file, just the
working directory outside .git, but that does not count, that working
directory is just used for the conversion, you should use only the .git
directory like:

git clone /path/to/tailor/working/dir/.git myproject

and you won't have the file under myproject.

So at the end I think this is just a user problem, it is not really a
bug in tailor.

^ Lele, that's why I'm not sending a patch. :-)

Attachment: pgpL8lYtaWlFW.pgp
Description: PGP signature

_______________________________________________
Tailor mailing list
[email protected]
http://lists.zooko.com/mailman/listinfo/tailor

Reply via email to