From: Pascal Obry <pascal@obry.net>
To: Peter Baumann <waste.manager@gmx.de>
Cc: git list <git@vger.kernel.org>
Subject: Re: Problem with git-svn
Date: Sun, 16 Dec 2007 16:40:07 +0100 [thread overview]
Message-ID: <476546D7.2030805@obry.net> (raw)
In-Reply-To: <20071216135625.GB4999@xp.machine.xx>
Pete,
> Eric made a fix[1] this week so git-svn won't get confused if e.g. trunk
> gets deleted and later created (or e.g. moved). Could you check if it
> also fixes your problem? At least there is some familiarity, because your
> trunk/PROJ also get moved from outside a path git-svn isn't tracking.
>
> -Peter
>
> [1]: See this thread for more details
> http://thread.gmane.org/gmane.comp.version-control.git/67665
This fix is already installed into the Git version I'm using which is:
git version 1.5.4.rc0.36.g7680
So there is something else...
Thanks,
Pascal.
--
--|------------------------------------------------------
--| Pascal Obry Team-Ada Member
--| 45, rue Gabriel Peri - 78114 Magny Les Hameaux FRANCE
--|------------------------------------------------------
--| http://www.obry.net
--| "The best way to travel is by means of imagination"
--|
--| gpg --keyserver wwwkeys.pgp.net --recv-key C1082595
next prev parent reply other threads:[~2007-12-16 15:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-16 10:30 Problem with git-svn Pascal Obry
2007-12-16 13:56 ` Peter Baumann
2007-12-16 15:40 ` Pascal Obry [this message]
2007-12-19 8:27 ` Eric Wong
2007-12-19 11:27 ` Pascal Obry
2007-12-20 18:30 ` Eric Wong
2007-12-20 20:33 ` Pascal Obry
2007-12-21 15:42 ` Pascal Obry
2007-12-22 4:29 ` Eric Wong
2007-12-22 14:38 ` Pascal Obry
2007-12-20 20:34 ` Pascal Obry
-- strict thread matches above, loose matches on Subject: below --
2008-08-19 13:41 Boaz Stuller
2008-08-20 8:11 ` Eric Wong
2008-08-20 17:45 ` Boaz Stuller
2008-08-21 6:34 ` Eric Wong
2007-05-03 23:10 John Wiegley
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=476546D7.2030805@obry.net \
--to=pascal@obry.net \
--cc=git@vger.kernel.org \
--cc=waste.manager@gmx.de \
/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).