git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Marcus D. Hanwell" <marcus@cryos.net>
To: git@vger.kernel.org, Peter Baumann <waste.manager@gmx.de>
Subject: git-svn init from Avogadro SVN repo - deleted files showing
Date: Sun, 09 Dec 2007 19:24:40 -0500	[thread overview]
Message-ID: <475C8748.6000005@cryos.net> (raw)

Hi,

I am quite new to git and git-svn but have been using both for my 
development work recently. I imported the Avogadro subversion repository 
(hosted on Sourceforge) using the following commands,

git svn init -t tags -b branches -T trunk 
https://avogadro.svn.sourceforge.net/svnroot/avogadro

git svn fetch


The files avogadro.pro and README in the trunk/ directory appear in my 
imported git repository but not in Avogadro subversion trunk. We also 
had trunk/src/ and all its files/subdirectories appearing in the git 
checkout but not in subversion trunk. We deleted this using git and git 
svn which removed it from the git checkouts too after r858.

I have been talking to Peter who confirmed this and pointed out that the 
repo was reorganised several times in the past. Please CC me on replies 
as I am not on the list. There is a copy of my git repo at 
http://platinum.cryos.net/avogadro.git/ if you would rather skip the 
import. Other than that everything has been working great. It would be 
good to get rid of this bug if possible. Let me know if there is 
anything else I can do to help.

Thanks,

Marcus

             reply	other threads:[~2007-12-10  0:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-10  0:24 Marcus D. Hanwell [this message]
2007-12-10 10:42 ` git-svn init from Avogadro SVN repo - deleted files showing Peter Baumann
2007-12-10 11:40   ` Peter Baumann
2007-12-13 16:41   ` Eric Wong
2007-12-13 18:13     ` Peter Baumann
2007-12-14 16:39       ` [PATCH] git-svn: handle our top-level path is deleted and later re-added Eric Wong
2007-12-14 16:43         ` Eric Wong
2007-12-15  0:24         ` cho
2007-12-15 16:35         ` Peter Baumann

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=475C8748.6000005@cryos.net \
    --to=marcus@cryos.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).