Re: [RFC] git email submissions

From: Matthias Urlichs <smurf@smurf.noris.de>
Date: Nov 16, 2005, 23:20 UTC
Message-ID: <pan.2005.11.16.23.19.58.895975@smurf.noris.de>
In-Reply-To: <437B73E2.3080903@pobox.com>

Hi, Jeff Garzik wrote:

> Smarter programs would send the overall description and pack file as 
> "[patch 0/N]", and then post the for-review patches in separate emails 
> as "[patch M/N]".

So you want to send the stuff twice? Ouch.

Seriously: We can mail patches, and we can re-base our changes.

Anything that's not covered by this is inherently complicated, such that specifying the starting point(s) of a git-send-pack-mail invocation needs to be handled by a program, else we *will* get *lots* of pilot errors.

Surprise: We already have a solution: host your archive someplace
and let git push+fetch handle everything.

-- 
Matthias Urlichs   |   {M:U} IT Design @ m-u-it.de   |  smurf@smurf.noris.de
Disclaimer: The quote was selected randomly. Really. | http://smurf.noris.de
 - -
Alan Turing thought about criteria to settle the question of whether
machines can think, a question of which we now know that it is about
as relevant as the question of whether submarines can swim.
		-- Dijkstra