From: Michael Haggerty <mhagger@alum.mit.edu>
To: edman747 <edman747@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Problem with git svn clone --authors-file
Date: Thu, 27 Oct 2011 08:58:17 +0200 [thread overview]
Message-ID: <4EA90109.4070504@alum.mit.edu> (raw)
In-Reply-To: <CABDh3gSsi9xwvw-6stw7URGK112LvF8Rt4XJeTwGM3q-tML=2Q@mail.gmail.com>
On 10/27/2011 01:51 AM, edman747 wrote:
> Hello,
> Attempting to clone a remote svn repo where I don't know all the
> previous SVN author names.
> installed msysgit (vista)
> gitbash,
> $ mkdir test
> $ cd test
>
> create authors file with a few known authors.
>
> $ git svn clone --authors-file=authors http://svn.repo/trunk
> ...
> runs fine until
> Author: (no author) not defined in authors file
>
> edit authors file add line: (no author) = none <email>
>
> ------
> rerun previous git svn command
>
> $ git svn clone --authors-file=authors http://svn.repo/trunk
> Using existing [svn-remote "svn"]
> svn-remote.svn.fetch already set to track :refs/remotes/git-svn
I'm not quite sure what your complaint is.
"git svn clone" is equivalent to a "git svn init" followed by "git svn
fetch". I would have thought that by the time "git svn clone" notices a
problem with the authors file, it would already be in the "git svn
fetch" phase. So it seems to me that after the first "clone" fails, one
should probably run "git svn fetch" instead of "git svn clone" again.
If this is the case (and the cause of your problem), then the
documentation and error message should be made clearer.
Michael
--
Michael Haggerty
mhagger@alum.mit.edu
http://softwareswirl.blogspot.com/
prev parent reply other threads:[~2011-10-27 6:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-26 23:51 Problem with git svn clone --authors-file edman747
2011-10-27 6:58 ` Michael Haggerty [this message]
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=4EA90109.4070504@alum.mit.edu \
--to=mhagger@alum.mit.edu \
--cc=edman747@gmail.com \
--cc=git@vger.kernel.org \
/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).