Re: git repository for ASDF

As I understand things, we should, if we are working on a particular
improvement, move ourselves onto a branch, make our changes, and then
offer up the changes for some flavor of review, right?

Can someone explain to me how the final step is done?  I have only done
this using org, where my changes were small enough that they could be
eyeballed in patch files.

But I have been working to get Marco's CLEAN-OP incorporated into ASDF,
and this involves adding files (notably in order to make tests).  This
puts me, I think, beyond the realm of easily reviewed patches.  In this
case does one provide a branch in the common-lisp.net repo?  Should one
create one's own public repository?

I have read some of the git tutorials but evidently I have not read the
right ones, since the answers to these questions still elude me.

I am very excited about the institution of the git repo, though, since
the changes I am making, although they are modest (and most of the work
is another's), they do involve non-local changes, and really seem to
exceed what one can comfortably do with CVS.

Best,
R

------------------------------------------------------------------------------
Register Now & Save for Velocity, the Web Performance & Operations 
Conference from O'Reilly Media. Velocity features a full day of 
expert-led, hands-on workshops and two days of sessions from industry 
leaders in dedicated Performance & Operations tracks. Use code vel09scf 
and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf