From: Jeff King <peff@peff.net>
To: James Gregory <j.gregory@epigenesys.co.uk>
Cc: git@vger.kernel.org
Subject: Re: git-fast-export is returning streams with source code inside
Date: Thu, 4 Aug 2011 01:05:28 -0600 [thread overview]
Message-ID: <20110804070528.GA11805@sigill.intra.peff.net> (raw)
In-Reply-To: <CAFC9htxwRg=+RD68hnnRy0hfptq23x3bL+xxHieK1evfFCTPjw@mail.gmail.com>
On Mon, Aug 01, 2011 at 12:57:58PM +0100, James Gregory wrote:
> I'm not sure if this is the right place to post bug reports - if not,
> please can you let me know.
This is the right place.
> I've found (what appears to be) a problem in git-fast-export. I've
> filed a bug in Launchpad, but I'm not sure if anyone from the Git
> community actively monitors it so I'm reporting it here to see if it
> can be fixed.
I don't think anybody monitors Launchpad explicitly; thanks for the
pointer.
> The bug can be viewed online at:
> https://bugs.launchpad.net/ubuntu/+source/git/+bug/815828
> and I've done my best to describe the bug in some detail. If you need
> me to elaborate on the problem further, don't hesitate to let me know.
Definitely looks like a bug. Is it possible for you to make the
offending repo available either publicly or to me in private? There's
not enough information in your report for me to reproduce the problem
here.
-Peff
next prev parent reply other threads:[~2011-08-04 7:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-01 11:57 git-fast-export is returning streams with source code inside James Gregory
2011-08-04 7:05 ` Jeff King [this message]
2011-08-04 9:08 ` James Gregory
2011-08-04 18:32 ` Jeff King
2011-08-05 9:24 ` James Gregory
2011-08-05 9:36 ` Jeff King
2011-08-05 9:54 ` James Gregory
2011-08-05 10:30 ` Jeff King
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=20110804070528.GA11805@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=j.gregory@epigenesys.co.uk \
/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).