From: Andrei Rybak <rybak.a.v@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: Obsolete instruction in SubmittingPatches?
Date: Thu, 1 Mar 2018 20:29:34 +0300 [thread overview]
Message-ID: <927e3166-9c60-fca5-ab41-f6d38380c1b1@gmail.com> (raw)
In-Reply-To: <xmqqd10okcfu.fsf@gitster-ct.c.googlers.com>
On 01.03.2018 0:54, Junio C Hamano wrote:
> Andrei Rybak <rybak.a.v@gmail.com> writes:
>
>> Is this part of guidelines obsolete, or am I not understanding this
>> correctly?
>
> I am merely being nice (but only on "time-permitting" basis).
>
Does that mean that the integration of a series is easier, when there is
a re-send?
next prev parent reply other threads:[~2018-03-01 17:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-28 21:31 Obsolete instruction in SubmittingPatches? Andrei Rybak
2018-02-28 21:54 ` Junio C Hamano
2018-03-01 17:29 ` Andrei Rybak [this message]
2018-03-01 21:43 ` 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
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=927e3166-9c60-fca5-ab41-f6d38380c1b1@gmail.com \
--to=rybak.a.v@gmail.com \
--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.
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).