Re: Converting commits to patch files? HEAD vs HEAD^

[Junio C Hamano <junkio@cox.net>]

>>>>> "MS" == Marc Singer <elf@buici.com> writes:

MS> If I've made several commits, I'd like to be able to gather several
MS> together and produce a patch file.  Better still, I'd like to be able
MS> to pick a set of discontiguous commits an bundle them into a single
MS> patch.  Ought I be using tags?

    You ought to be using ...

Oh, I want to say it because the above is what I do all the time
using my Porcelain on GIT, but on the other hand, officially I
am _not_ working on any Porcelain, so... I am in a dilemma.  I
won't talk about that tool I use myself.

Although I have not looked at it myself, you may want to take a
look at StGIT.

"Keeping patches, tracking upstream by primarily updating,
forward porting and e-mail submitting patches" is often the
development model taken by "individual developers", while
"making commits primarily by accepting patches, merging with
repos of other people who have similar aggregator role" is often
the model used by "project leads".

The core GIT (and "git" barebone Porcelain) is geared towards
"project lead" use, and I suspect Cogito would be so to a
certain extent.  By judging only from its description, StGIT,
with its attitude ancestry of quilt, may be more comfortable to
use with "individual developers" mode of operation.

Well, I'd say what I use anyway, and quickly duck ;-)

    You ought to be using ... JIT.