In a previous instance of the APAC meeting of the Gluster community I
had mentioned about looking at the component update section and
considering providing a report on the untriaged bug load. The
rationale is to ensure that instead of a large mess of "unknown" bugs,
the maintainers (and thus the
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20200121T06Z
DTEND:20200121T071500Z
DTSTAMP:20200114T065907Z
ORGANIZER;CN=a...@kadalu.io:mailto:a...@kadalu.io
UID:6av0mbo57jmrv4t5cctsm5p...@google.com
On Fri, Jan 10, 2020 at 10:55 AM Sankarshan Mukhopadhyay <
sankarshan.mukhopadh...@gmail.com> wrote:
> I had mentioned that I'll reach out to Amar to urge about making
> progress on Gluster 8. We did have a conversation and upon reviewing
> the present state of the list of issues/features with
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20200114T06Z
DTEND:20200114T07Z
DTSTAMP:20200113T121510Z
ORGANIZER;CN=srako...@redhat.com:mailto:srako...@redhat.com
On Mon, Jan 13, 2020 at 9:41 AM Yaniv Kaul wrote:
> To conclude and ensure I understood both:
> - I've sent a patch to remove extra_free parameter (and the associated
> gf_memdup() in 2 places) -
> https://review.gluster.org/#/c/glusterfs/+/23999/ (waiting for CI to
> finish working on it).
> -
To conclude and ensure I understood both:
- I've sent a patch to remove extra_free parameter (and the associated
gf_memdup() in 2 places) -
https://review.gluster.org/#/c/glusterfs/+/23999/ (waiting
for CI to finish working on it).
- I'll send a patch to remove extra_stdfree - but this one is
