From: Eric Wong <normalperson@yhbt•net>
To: Valery Yundin <yuvalery@gmail•com>
Cc: git@vger•kernel.org
Subject: Re: git svn import failure : write .git/Git_svn_hash_BmjclS: Bad file descriptor
Date: Thu, 29 Jan 2015 23:34:30 +0000 [thread overview]
Message-ID: <20150129233429.GA7162@dcvr.yhbt.net> (raw)
In-Reply-To: <CABNxngNDwf_Cy77OzvMg__kCNoTz5y1a2KKG1vobYjE_m_aLkQ@mail.gmail.com>
Valery Yundin <yuvalery@gmail•com> wrote:
> Tested on:
> git-svn version 2.3.0.rc2 (svn 1.8.11) - FAIL
> git-svn version 2.2.2 (svn 1.8.10) - FAIL
> git-svn version 1.8.4.5 (svn 1.8.11) - WORKS
Thank you for that info. Do you think you can bisect which
versions/revisions of git-svn introduced that failure for us? I don't
have much time this part of the year for git-svn, but maybe it's related
to the performance work we did around fall 2014.
Thanks again.
next prev parent reply other threads:[~2015-01-29 23:34 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-29 22:03 git svn import failure : write .git/Git_svn_hash_BmjclS: Bad file descriptor Valery Yundin
2015-01-29 23:34 ` Eric Wong [this message]
2015-01-29 23:59 ` Valery Yundin
2015-01-30 0:22 ` Eric Wong
2015-01-30 0:40 ` Valery Yundin
2015-01-30 1:30 ` Eric Wong
2015-01-31 12:51 ` Nico Schlömer
2015-01-31 14:52 ` Valery Yundin
2015-02-12 19:18 ` Eric Wong
2015-02-16 15:10 ` Nico Schlömer
2015-02-17 6:17 ` Eric Wong
2015-02-25 10:19 ` Kyle J. McKay
[not found] ` <CAK6Z60fqEkM_tON6tcnwBqJzBCvLB=eVJdyXSnNb7N1iR_DSsw@mail.gmail.com>
2015-02-25 20:08 ` Eric Wong
2015-02-25 20:33 ` Kyle J. McKay
[not found] <CAK6Z60ciheWOUGOv1sYcA==B2WR1Rs_eMU+9a=R3FBwc_37CyQ@mail.gmail.com>
2015-02-26 9:09 ` Nico Schlömer
2015-02-26 13:49 ` Kyle J. McKay
2015-02-26 21:27 ` Eric Wong
2015-03-23 19:11 ` Junio C Hamano
2015-03-23 19:36 ` Eric Wong
2015-03-23 19:56 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2015-01-16 17:13 Mike
2015-01-08 12:43 Minty
2015-01-08 17:51 ` Minty
2015-01-14 1:50 ` Eric Wong
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=20150129233429.GA7162@dcvr.yhbt.net \
--to=normalperson@yhbt$(echo .)net \
--cc=git@vger$(echo .)kernel.org \
--cc=yuvalery@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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