[drupal-docs] [support] How to use CVS tags and branches to keep track of different uncommited patches.

[sepeck]

Issue status update for 
http://drupal.org/node/33603
Post a follow up: 
http://drupal.org/project/comments/add/33603

 Project:      Documentation
 Version:      <none>
 Component:    Developer Guide
 Category:     support requests
 Priority:     normal
 Assigned to:  Anonymous
 Reported by:  beginner
 Updated by:   sepeck
 Status:       active

There are instructions here.
http://drupal.org/node/28245


I test by sync'ing up and building seperate site's based on what
patches I intend to apply.




sepeck



Previous comments:
------------------------------------------------------------------------

Mon, 10 Oct 2005 10:09:40 +0000 : beginner

Hello,


I am currently learning how to use CVS so that I can modify HEAD and
contribute some patches.


I have read (many times) the relevant pages in the handbook, as well as
the cvsbook.red-bean.com. I have created a local cvs repository and
checked out then commited drupal HEAD into my repository.


It is said that each patch should be kept separate, each being specific
to a function, a bug, etc... So, how, concretely speaking, do you keep
track of each patch.  Do you create a branch for each specific patch?


Supposed I'm working on bug1 -> patch1, bug2-> patch2 and mymodule and
myfeature3 -> patch3, myfeature4 -> patch4.
Patch1 ... patch4 have not been commited to Drupal HEAD, so I try to
keep them up to date within my local ropository. How do I keep them
upto date, separate from each other, and what do I do once one of them
is actually commited to Drupal HEAD....


Thanks.