From: Jakub Narebski <jnareb@gmail.com>
To: "David E. Wheeler" <david@kineticode.com>
Cc: Eric Wong <normalperson@yhbt.net>, git@vger.kernel.org
Subject: Re: Again with git-svn: File was not found in commit
Date: Sun, 26 Apr 2009 01:17:28 -0700 (PDT) [thread overview]
Message-ID: <m31vrfq11w.fsf@localhost.localdomain> (raw)
In-Reply-To: <81EFD289-5E46-4B27-8DA4-C2039915CE2D@kineticode.com>
"David E. Wheeler" <david@kineticode.com> writes:
> On Apr 25, 2009, at 6:53 PM, Eric Wong wrote:
>
> > Hopefully the workaround is working out for you.
>
> [Finally], yes.
>
> [Finally]: http://justatheory.com/computers/vcs/git/bricolage-to-git.html
Thank you for posting this detailed analysis.
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2009-04-26 8:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-13 18:08 Again with git-svn: File was not found in commit David E. Wheeler
2009-04-21 18:02 ` Eric Wong
2009-04-21 18:16 ` David E. Wheeler
2009-04-26 1:53 ` Eric Wong
2009-04-26 2:40 ` David E. Wheeler
2009-04-26 8:17 ` Jakub Narebski [this message]
2009-04-27 0:27 ` David E. Wheeler
2009-04-28 9:40 ` Jakub Narebski
2009-04-28 16:15 ` David E. Wheeler
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=m31vrfq11w.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=david@kineticode.com \
--cc=git@vger.kernel.org \
--cc=normalperson@yhbt.net \
/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).