Why don't you check out another clone of the source and start your own personal branch. Then merge with upstream when you feel it is appropriate.
On Thu, Jun 26, 2008 at 7:06 AM, Angelo Turetta < [EMAIL PROTECTED] <[EMAIL PROTECTED]>> wrote: > Scott Ullrich wrote: > >> On Wed, Jun 25, 2008 at 12:47 PM, Angelo Turetta >> <[EMAIL PROTECTED] <[EMAIL PROTECTED]>> wrote: >> >>> I hope the migration to git goes well, I promise I'll try to help you if >>> I >>> can save my work locally and not redo it every time from scratch. >>> >> >> custom_overlay is not sufficient? >> > > No, It isn't. Maybe I'm old-fashioned, but I think the source files should > be left unmodified by the build process. If I change a .php file, I expect > that after the build the file is still the same. > The problem is that custom_overlay appeared only recently (I did my largest > efforts two years ago), and it doesn't help when I want to patch some files > but still receive the upstream changes to those same files. If I put a > changed php file in custom_overlay, I have to manually merge every check-in > from the pfSense repo. > > I'm sure git will be THE solution, and will also attract more contributions > to the project. > > Thanks again, > Angelo. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
