Osamu Aoki:
>
> Maybe before discussing technical solutions, we should know what issues
> we are addressing by this modification. Is there a real cases which you
> need to have this patch?
>
I need this for rustc. Try "apt-get source rustc" now and "uscan --verbose", it
will fail. I had to
Hi,
On Tue, Jan 23, 2018 at 03:58:11PM +0100, Mattia Rizzolo wrote:
> On Tue, Jan 23, 2018 at 10:58:53PM +0900, Osamu Aoki wrote:
> > This looks a reasonable patch. But I don't know why you chose
> > 16384=0x400 as the max figure.
... (It's ARG_MAX is in BYTEs but ...)
> Jan 13 21:39:31
Osamu Aoki:
> Hi,
>
> [..]
>
> This looks a reasonable patch. But I don't know why you chose
> 16384=0x400 as the max figure.
>
> Following your comment, I tried on my local machine
> $ getconf ARG_MAX
> 2097152
>
> This is bigger than 16384.
>
> If this is different on different system, why
On Tue, Jan 23, 2018 at 10:58:53PM +0900, Osamu Aoki wrote:
> This looks a reasonable patch. But I don't know why you chose
> 16384=0x400 as the max figure.
>
> Following your comment, I tried on my local machine
> $ getconf ARG_MAX
> 2097152
>
> This is bigger than 16384.
>
> If this is
Hi,
On Sat, Jan 13, 2018 at 04:23:34PM +, Ximin Luo wrote:
> This is an automated email from the git hooks/post-receive script.
>
> infinity0 pushed a commit to branch pu/mk-origtargz-argmax
> in repository devscripts.
>
> commit 3fa9a36bb4f352c07a3537cb597aaf734ce936f1
> Author: Ximin Luo