Rails - Feb 2005 - The protocol for posting multiple patches

Hi all,

I have posted a patch for Active Record to add a particular feature (feature
A).

If I make some more changes to the same files, in order to implement another
feature (feature B), and then generate another diff, I will end up with a
patch that includes the changes needed for both feature A and feature B.

If feature B does not depend on feature A, should I generate a patch that
implements only feature B?  How would I go about doing that?

Adelle.

Adelle Hartley wrote:
> If I make some more changes to the same files, in order to implement
another
> feature (feature B), and then generate another diff, I will end up with a
> patch that includes the changes needed for both feature A and feature B.
> 
> If feature B does not depend on feature A, should I generate a patch that
> implements only feature B?  How would I go about doing that?
Implement features A and B in fresh svn checkouts.  Maintaining multiple
parallel lines of development in this manner becomes painful very quickly.

In an ideal world, you could branch the source for your own features and
diff with trunk to generate patches, but you can''t do that with a
read-only repository.

Enter svk, a distributed source control manager based on svn.  You can
mirror a read-only svn repository, create and commit to local branches,
then merge with the mirrored repository to create a patch.  Second to
Rails, it''s my favorite new software.

  http://svk.elixus.org/

Zealously,
jeremy