Re: git repository for ASDF

Gary King wrote:
> Hi Robert,
> 
>> 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?
> 
> I'm pretty new to git myself but am trying to use something like this  
> workflow
> 
> http://reinh.com/blog/2009/03/02/a-git-workflow-for-agile-teams.html
> 
>> 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.
> 
> A Nikodemus suggested, I think sending a patch to the mailing list  
> would be the best thing for now.

My concern arose about shipping around patches involving the addition of
multiple files (this arises when creating new tests for asdf).
[...snip...]
> 
>> 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.
> 
> Yeah! Why don't you send the patch when you're ready and we can try to  
> make asdf:clean-op a test case.

Will do.  I shelved this for a long while because I wasn't sure how to
deal with creating the new test cases with only CVS to rely on.  Might
take me a little while to recover the context.

Best,
R



------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com