git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Thomas Braun <thomas.braun@virtuell-zuhause.de>
To: tboegi@web.de, git@vger.kernel.org
Subject: Re: [PATCH v2 1/1] Use size_t instead of 'unsigned long' for data in memory
Date: Wed, 16 Jan 2019 22:46:13 +0100	[thread overview]
Message-ID: <5b9d020c-00cb-9340-b21f-f16f7fceb8cf@virtuell-zuhause.de> (raw)
In-Reply-To: <20181120050456.16715-1-tboegi@web.de>

Am 20.11.2018 um 06:04 schrieb tboegi@web.de:

I'm interested in helping getting this forward!

> What we really need for this patch to fly are this branches:
> mk/use-size-t-in-zlib

In pu.

> tb/print-size-t-with-uintmax-format

in master.

> And then it is rebased on top of all cooking stuff, too many branches
> to be mentioned here.
> 
> It may be usefull to examine all "unsigned long" which are left after
> this patch and turn them into (what ? unsigned int? size_t? uint32_t ?).
> And once they are settled, re-do this patch with help of a coccinelle script.
> I don't know.
> I probably will rebase it until Junio says stop or someone else comes with
> a better solution.

I could not spot this series in the cooking list so what is good way
forward?

  parent reply	other threads:[~2019-01-16 21:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-17 15:11 [PATCH/RFC v1 1/1] Use size_t instead of unsigned long tboegi
2018-11-18 20:18 ` Derrick Stolee
2018-11-18 23:40   ` Junio C Hamano
2018-11-19  5:33     ` Torsten Bögershausen
2018-11-19 18:15       ` René Scharfe
2018-11-19 16:33   ` Torsten Bögershausen
2018-11-20  1:36     ` Junio C Hamano
2018-11-20  5:04 ` [PATCH v2 1/1] Use size_t instead of 'unsigned long' for data in memory tboegi
2018-11-21 11:55   ` Derrick Stolee
2019-01-16 21:46   ` Thomas Braun [this message]
2019-01-19 17:06     ` Torsten Bögershausen
2019-01-22 14:25       ` Thomas Braun
2019-04-13 15:18 ` [PATCH v3 " tboegi

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: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=5b9d020c-00cb-9340-b21f-f16f7fceb8cf@virtuell-zuhause.de \
    --to=thomas.braun@virtuell-zuhause.de \
    --cc=git@vger.kernel.org \
    --cc=tboegi@web.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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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).