public-inbox.git - an "archives first" approach to mailing lists

Date	Commit message (Collapse)
2019-01-20	solver: remove extra "^index $OID..$OID" line viewdiff
	It was harmless, besides wasting space and memory.
2019-01-20	solver: force quoted-printable bodies to LF
	..if the Email::MIME ->crlf is LF. Email::MIME::Encodings forces everything to CRLF on quoted-printable messages for RFC-compliance; and git-apply --ignore-whitespace seems to miss a context line which is just "\r\n" (w/o leading space).
2019-01-20	solver: restore diagnostics and deal with CRLF
	Apparently Email::MIME returns quoted-printable text with CRLF. So use --ignore-whitespace with git-apply(1) and ensure we don't capture '\r' in pathnames from those emails. And restore "$@" dumping when we die while solving.
2019-01-20	solver: add a TODO note about making this fully evented
	Applying a 100+ patch series can be a pain and lead to a wayward client monopolizing the connection. On the other hand, we'll also need to be careful and limit the number of in-flight file descriptors and parallel git-apply processes when we move to an evented model, here.
2019-01-20	solver: note the synchronous nature of index preparation
	It's not likely to be worth our time to support a callback-driven model for something which happens once per patch series.
2019-01-20	solver: break @todo loop into a callback
	This will allow each patch search via Xapian to "yield" the current client in favor of another client in the PSGI web interface for fairness.
2019-01-20	solver: simplify control flow for initial loop
	We'll be breaking this up into several steps, too; since searching inboxes for patch blobs can take 10s of milliseconds for me.
2019-01-20	solver: switch patch application to use a callback
	A bit messy at the moment, but we need to break this up into smaller steps for fairness with other clients, as applying dozens of patches can take several hundred milliseconds.
2019-01-20	solver: break up patch application steps
	We want more fine-grained scheduling for PSGI use, as the patch application step can take hundreds of milliseconds on my modest hardware
2019-01-20	solver: more verbose blob resolution
	Help users find out where each step of the resolution came from. Also, we must clean abort the process if we have missing blobs. And refine the output to avoid unnecessary braces, too.
2019-01-19	solver: operate directly on git index
	No need to incur extra I/O traffic with a working-tree and uncompressed files on the filesystem. git can handle patch application in memory and we rely on exact blob matching anyways, so no need for 3way patch application.
2019-01-19	solver: various bugfixes and cleanups
	Remove the make_path dependency and call mkdir directly. Capture mode on new files, avoid referencing non-existent functions and enhance the debug output for users to read.
2019-01-19	solver: initial Perl implementation
	This will lookup git blobs from associated git source code repositories. If the blobs can't be found, an attempt to "solve" them via patch application will be performed. Eventually, this may become the basis of a type-agnostic frontend similar to "git show"