From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [BUG?] bulk checkin does not respect filters
Date: Fri, 24 Feb 2012 04:39:24 -0500 [thread overview]
Message-ID: <20120224093924.GA11680@sigill.intra.peff.net> (raw)
In-Reply-To: <20120224082803.GB18688@sigill.intra.peff.net>
On Fri, Feb 24, 2012 at 03:28:03AM -0500, Jeff King wrote:
> I don't like repeating all of the convert_to_git policy logic. Perhaps
> if you pass a NULL buffer to convert_to_git, it should run through its
> usual logic, stopping just short of actually writing anything, and
> return a flag indicating whether it _would_ convert...
So here's a series that does that.
[1/2]: teach convert_to_git a "dry run" mode
[2/2]: do not stream large files to pack when filters are in use
-Peff
next prev parent reply other threads:[~2012-02-24 9:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-24 3:02 [BUG?] bulk checkin does not respect filters Jeff King
2012-02-24 3:17 ` Junio C Hamano
2012-02-24 3:42 ` Junio C Hamano
2012-02-24 7:54 ` Jeff King
2012-02-24 18:48 ` Junio C Hamano
2012-02-24 8:28 ` Jeff King
2012-02-24 9:39 ` Jeff King [this message]
2012-02-24 9:41 ` [PATCH 1/2] teach convert_to_git a "dry run" mode Jeff King
2012-02-24 9:48 ` [PATCH 2/2] do not stream large files to pack when filters are in use Jeff King
2012-02-24 20:03 ` Junio C Hamano
2012-02-24 20:48 ` Jeff King
2012-02-24 21:01 ` Jeff King
2012-02-24 21:20 ` Junio C Hamano
2012-02-24 21:19 ` Jeff King
2012-02-24 22:02 ` [PATCHv2 1/3] teach convert_to_git a "dry run" mode Jeff King
2012-02-24 22:05 ` [PATCHv2 2/3] teach dry-run convert_to_git not to require a src buffer Jeff King
2012-02-24 22:10 ` [PATCHv2 3/3] do not stream large files to pack when filters are in use Jeff King
2012-02-24 22:42 ` [PATCH 2/2] " Junio C Hamano
2012-02-24 20:03 ` [BUG?] bulk checkin does not respect filters Junio C Hamano
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=20120224093924.GA11680@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).