unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Wolfgang Denk <wd@denx.de>, libc-alpha@sourceware.org
Cc: Lukasz Majewski <lukma@denx.de>
Subject: Re: Accelerating Y2038 glibc fixes
Date: Tue, 16 Jul 2019 17:20:36 +0530	[thread overview]
Message-ID: <2a129837-9fe4-8f37-2b0d-2086a2f8253b@gotplt.org> (raw)
In-Reply-To: <20190712072103.D3DBC24003A@gemini.denx.de>

Hello Wolfgang,

I haven't been involved in the Y2038 issue so I cannot comment on the
content or quality of the patches or the way forward in that context.
However I want to assure you that we're collectively trying our best to
review patches that come on the list, just that there aren't enough
hands to help.  glibc is a central project in the Linux ecosystem but
unfortunately it's not as well staffed as other projects such as the
kernel or gcc.  Things have gotten much better in the last few years,
but we're still short of people as many of us are doing other things
alongside glibc.

Hopefully someone with more context and will respond soon and help
unblock things but until then, please don't lose hope, we will get there
eventually!

Siddhesh


On 12/07/19 12:51 PM, Wolfgang Denk wrote:
> See for example [1] - there are just 7 lines of "code".  But Joseph
> does not accept our patches.  The arguments he gives are not on a
> technical level; instead he says that only a native English speaker
> who has a with deep understanding of glibc internals and the
> previous development process will be capable to provide such a patch
> in an acceptable way.
> 
> To be honest - I think only himself would fulfill this requirement
> good enough.
> 
> But Joseph has not enough resources available, and he cannot
> allocate more resources even if such efforts would be paid for by
> DENX.  And he does not know of anyone to help.
> 
> In short, we are stuck, and not even proper funding can accelerate
> the process - not to mention, that it's impossible to give any
> deadlines at all.
> 
> 
> Obviously, this is just my personal and external view - I guess I
> must be missing something, because I cannot imagine that the progress
> of a project that plays such a central role to the whole FOSS
> community suffers from such bottlenecks, and that these cannot be
> helped.
> 
> Is there anything we can do to accelerate this process?  As
> mentioned, we are willing to dedicate both man-power and/or money,
> if this helps.
> 
> Thanks in advance!
> 
> [1] https://patchwork.ozlabs.org/patch/1114061/
> 
> 
> 
> Best regards,
> 
> Wolfgang Denk
> 


  parent reply	other threads:[~2019-07-16 11:51 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-12  7:21 Accelerating Y2038 glibc fixes Wolfgang Denk
2019-07-16  9:32 ` Wolfgang Denk
2019-07-16 11:50 ` Siddhesh Poyarekar [this message]
2019-07-16 12:40   ` Wolfgang Denk
2019-07-16 12:44 ` Florian Weimer
2019-07-16 14:52   ` Wolfgang Denk
2019-07-16 15:09     ` Florian Weimer
2019-07-16 15:19       ` Andrew Pinski
2019-07-17 14:15     ` Arnd Bergmann
2019-07-17 14:41       ` Florian Weimer
2019-07-17 16:00         ` Wolfgang Denk
2019-07-17 16:04           ` Florian Weimer
2019-07-17 16:18             ` Lukasz Majewski
2019-07-18 18:53               ` Adhemerval Zanella
2019-07-18 19:13                 ` Florian Weimer
2019-07-18 20:31                   ` Adhemerval Zanella
2019-07-18 21:20                     ` Florian Weimer
2019-07-18 22:32                     ` Paul Eggert
2019-07-19  7:21                       ` Andreas Schwab
2019-07-19  3:06                     ` Rich Felker
2019-07-19 17:44                       ` Adhemerval Zanella
2019-07-19 19:03                         ` Alistair Francis
2019-07-25 20:40                 ` Joseph Myers
2019-07-29 17:47                   ` Adhemerval Zanella
2019-07-29 19:58                     ` Joseph Myers
2019-07-29 21:00                       ` Adhemerval Zanella
2019-07-29 21:08                         ` Joseph Myers
2019-07-29 23:12                           ` Paul Eggert
2019-07-29 23:30                             ` Joseph Myers
2019-07-17 17:50       ` Rich Felker
2019-07-17 21:57         ` Lukasz Majewski
2019-07-17 22:37           ` Rich Felker
2019-07-18  7:20             ` Lukasz Majewski
2019-07-18 13:35               ` Rich Felker
2019-07-18 14:47           ` Rich Felker
2019-07-18 14:49             ` Florian Weimer
2019-07-18 15:46               ` Rich Felker
2019-07-18 16:43                 ` Adhemerval Zanella
2019-07-20  4:43             ` Rich Felker
2019-07-25 19:54 ` Joseph Myers
2019-07-26 10:39   ` Lukasz Majewski
2019-07-29 18:55     ` Zack Weinberg
2019-07-29 20:12       ` Joseph Myers
2019-07-30 11:02         ` Lukasz Majewski
2019-07-30 12:24           ` Joseph Myers
2019-07-30 14:04       ` Lukasz Majewski
2019-08-09  7:25         ` Lukasz Majewski
     [not found]           ` <CAKCAbMhOMQ9yTFpy+OQkDvZPPFf_fFn6oSxjvLTaUwC4jpPRag@mail.gmail.com>
2019-08-09 12:32             ` Fwd: " Zack Weinberg
2019-07-30 19:58       ` Joseph Myers
2019-07-30 20:28         ` Florian Weimer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/libc/involved.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2a129837-9fe4-8f37-2b0d-2086a2f8253b@gotplt.org \
    --to=siddhesh@gotplt.org \
    --cc=libc-alpha@sourceware.org \
    --cc=lukma@denx.de \
    --cc=wd@denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).