From: "Torsten Bögershausen" <tboegi@web.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v2 1/1] remote-curl.c: xcurl_off_t is not portable (on 32 bit platfoms)
Date: Mon, 12 Nov 2018 06:20:39 +0100 [thread overview]
Message-ID: <20181112052039.GA12275@tor.lan> (raw)
In-Reply-To: <xmqqbm6v3qex.fsf@gitster-ct.c.googlers.com>
On Mon, Nov 12, 2018 at 12:50:30PM +0900, Junio C Hamano wrote:
> tboegi@web.de writes:
>
> >
> > This is a re-semd, the orignal patch was part of a 2
> > patch-series.
> > This patch needed some rework, and here should be
> > the polished version.
>
> Will queue.
Thanks, is there a chance to kill a typo here ?
s/comopared/compared/
- A temporally variable "size" is used, promoted int uintmax_t and the comopared
> Next time, please refrain from saying "re-send", if you
> changed anything in the patch (or the log message), as the phrase
> implies you are sending the same thing as before (just in case the
> earlier one was not seen, for example). Marking it as vN+1 like you
> did for this patch and having a reference to the original would make
> it clear, though ;-)
Sorry for the confusion.
The next time I will not send unrelated patches as a series,
so that we have a better "Message-ID:" and "In-Reply-To:"
flow (which should make live 3% easier).
https://public-inbox.org/git/20181029165914.2677-1-tboegi@web.de/
https://public-inbox.org/git/20181109174110.27630-1-tboegi@web.de/
next prev parent reply other threads:[~2018-11-12 5:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-25 16:13 [PATCH v1 2/2] curl_off_t xcurl_off_t is not portable tboegi
2018-10-26 2:48 ` Junio C Hamano
2018-10-26 15:15 ` Torsten Bögershausen
2018-10-29 16:59 ` [PATCH v2 1/1] remote-curl.c: xcurl_off_t is not portable (on 32 bit platfoms) tboegi
2018-11-09 17:41 ` tboegi
2018-11-12 3:50 ` Junio C Hamano
2018-11-12 5:20 ` Torsten Bögershausen [this message]
2018-11-12 8:03 ` Junio C Hamano
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181112052039.GA12275@tor.lan \
--to=tboegi@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.