Re: [PATCH v3 01/20] linear-assignment: a function to solve least-cost assignment problems
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Jul 6, 2018, 22:43 UTC
- Message-ID
- <xmqqtvpcgf40.fsf@gitster-ct.c.googlers.com>
- In-Reply-To
- <39272eefcfe66de3ca1aa2ee43d6626ce558caae.1530617166.git.gitgitgadget@gmail.com>
"Johannes Schindelin via GitGitGadget" <gitgitgadget@gmail.com> writes:
Show 15 quoted lines
> From: Johannes Schindelin <johannes.schindelin@gmx.de> > > The problem solved by the code introduced in this commit goes like this: > given two sets of items, and a cost matrix which says how much it > "costs" to assign any given item of the first set to any given item of > the second, assign all items (except when the sets have different size) > in the cheapest way. > > We use the Jonker-Volgenant algorithm to solve the assignment problem to > answer questions such as: given two different versions of a topic branch > (or iterations of a patch series), what is the best pairing of > commits/patches between the different versions? > > Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> > ---
Does the "gitgitgadget" thing lie on the Date: e-mail header?
Postdating the patch with in-body header is fine, but mailbox tools often use and trust the Date: timestamp when sorting and finding messages etc. so sending a new patch to add linear-assignment.c that is different from what was added 9 weeks ago with "Date: Mon, 30 Apr 2018" header can easily cause me to miss that message when I look for things that happened within the past few weeks, for example.