From: "Lars Hjemli" <lh@elementstorage.no>
To: git <git@vger.kernel.org>, "Eric Wong" <normalperson@yhbt.net>
Subject: Re: [BUG] git-svn dcommit fails (connection closed unexpectedly)
Date: Fri, 11 May 2007 13:27:19 +0200 [thread overview]
Message-ID: <8c5c35580705110427o4de686e8qdb37f6a2da0043e4@mail.gmail.com> (raw)
In-Reply-To: <vpq7irfengj.fsf@bauges.imag.fr>
On 5/11/07, Matthieu Moy <Matthieu.Moy@imag.fr> wrote:
> Hi,
>
> I'm using git-svn, which usually works fine, but I occasionally get
> this:
>
> $ git-svn dcommit
> A file1
> A file2
> Network connection closed unexpectedly: Connection closed unexpectedly at /path/to/git-svn line 401
Is this happening if you dcommit a file in a new directory?
The reason I'm asking is that I see the same problem in that
situation, but my svn repo is on a windows box, accessed over
svn://url, so I just assumed it was a problem on the remote end (the
service dies). But the problem always goes away if I commit the new
directory using the svn client before doing git-svn dcommit again....
--
larsh
next prev parent reply other threads:[~2007-05-11 11:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-11 9:09 [BUG] git-svn dcommit fails (connection closed unexpectedly) Matthieu Moy
2007-05-11 11:27 ` Lars Hjemli [this message]
2007-05-11 11:30 ` Lars Hjemli
2007-05-11 12:51 ` Matthieu Moy
2007-05-14 18:13 ` Matthieu Moy
2007-05-19 6:14 ` Eric Wong
2007-05-19 9:58 ` [PATCH] git-svn: avoid crashing svnserve when creating new directories Eric Wong
2007-05-19 10:19 ` Matthieu Moy
2007-05-19 10:58 ` Eric Wong
2007-05-19 12:02 ` Matthieu Moy
2007-05-13 17:17 ` [BUG] git-svn dcommit fails (connection closed unexpectedly) Eric Wong
2007-05-13 17:49 ` Martin Eisenhardt
2007-05-13 18:24 ` Karl Hasselström
2007-05-13 21:01 ` Eric Wong
2007-05-14 0:39 ` Eric Wong
2007-05-14 17:26 ` Linus Torvalds
2007-05-14 17:50 ` Matthieu Moy
2007-05-14 12:27 ` Matthieu Moy
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=8c5c35580705110427o4de686e8qdb37f6a2da0043e4@mail.gmail.com \
--to=lh@elementstorage.no \
--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).