Re: [PATCH] compat: move strdup(3) replacement to its own file

Hi, On Wed, 7 Sep 2016, Junio C Hamano wrote: > René Scharfe writes: > > > Well, OK. I think the missing point is that the original nedmalloc > > doesn't come with strdup() and doesn't need it. Only _users_ of > > nedmalloc need it. Marius added it in nedmalloc.c, but strdup.c

Re: [PATCH] compat: move strdup(3) replacement to its own file

René Scharfe writes: > Well, OK. I think the missing point is that the original nedmalloc > doesn't come with strdup() and doesn't need it. Only _users_ of > nedmalloc need it. Marius added it in nedmalloc.c, but strdup.c is a > better place for it. Thanks. I'll add these

Re: [PATCH] compat: move strdup(3) replacement to its own file

Am 04.09.2016 um 09:46 schrieb Johannes Schindelin: Hi René, I imagine you Cc:ed me because the nedmalloc stuff came in via the Windows port, contributed by Marius (who is no longer active on the Git project because it works well enough for him)? Kind of; it's also a follow-up to the recent

Re: [PATCH] compat: move strdup(3) replacement to its own file

Hi René, I imagine you Cc:ed me because the nedmalloc stuff came in via the Windows port, contributed by Marius (who is no longer active on the Git project because it works well enough for him)? On Sat, 3 Sep 2016, René Scharfe wrote: > Move our implementation of strdup(3) out of

[PATCH] compat: move strdup(3) replacement to its own file

Move our implementation of strdup(3) out of compat/nedmalloc/ and allow it to be used independently from USE_NED_ALLOCATOR. This reduces the difference of our copy of nedmalloc from the original, making it easier to update, and allows for easier testing and reusing of our version of strdup().