[Clam-devel] Branches again?

[Xavier Amatriain]

When you are refactoring the Spectrum class there is no way you can 
avoid having "a bunch of local changes".

I see your point in the proposed working method based on patch but I 
think you are forgetting that CLAM is a
framework, not a single app. If I am working in my particular app, which 
uses and may extend the framework
(be it a real-time gender change, a plugin, or neural networks), having 
to work over a long discussion every time
I do a small increment is not very functional.

That's when I see branches being useful.

Pau Arumí wrote:
> Just a small follow up:
>
> En/na Xavier Amatriain ha escrit:
>> now that we are all much more educated it wouldn't hurt (at least not 
>> as much as me having my local sanbox with
>> a bunch of code I can't commit anywhere :)
> But why keeping a bunch of local changes? If you see integration 
> issues, don't commit them, send a patch to discuss it first.
>
> But please let's put high priority (and i commit to it) on keeping all 
> sandboxes in sync with svn. and of course, don't wait to have "a lot" 
> of changes to do this...
>
> Pau
>
>
> _______________________________________________
> Clam-devel mailing list
> Clam-devel at llistes.projectes.lafarga.org
> https://llistes.projectes.lafarga.org/cgi-bin/mailman/listinfo/clam-devel