10 Sep
2013
10 Sep
'13
4:35 a.m.
On 9 September 2013 17:53, Antonio Quartulli <antonio(a)meshcoding.com> wrote:
On Mon, Sep 09, 2013 at 05:05:47PM +0300, Mihail
Costea wrote:
I took a small rest last week and now I'm redoing everything.
I was thinking about sending the first part for merging (the one with
generalization the DAT).
That is the one that needs most rewriting every time because it
affects the most existing code.
The rest I think I can send them together.
Hi Antonio,
Is it possible to send the new model for the generalization as a patch
first (the part without IPv6), or maybe everything as a patch as once?
Having 5-6 patches to rewrite every time something changes makes the
development harder.
Which patches do you want to merge?
If they are ready it is better to send them as PATCH to the ml and then base
your work on top of them assuming they will be merged at some point.
Cheers,
p.s. welcome to the rebase nightmare ;)
--
Antonio Quartulli
..each of us alone is worth nothing..
Ernesto "Che" Guevara
Thanls,
Mihail
--
Mihail Costea