Re: git pull defaults for recursesubmodules

From: Junio C Hamano <gitster@pobox.com>
Date: Oct 25, 2018, 10:09 UTC
Message-ID: <xmqqy3amficw.fsf@gitster-ct.c.googlers.com>
In-Reply-To: <CAGshahk7pY4rW5SQu73AdHMmxsbDCo5UP5LGF67FQYBws492TA@mail.gmail.com>

Tommi Vainikainen <tvainika@gmail.com> writes:

> After reading SubmittingPatches I didn't find if I should now send a
> fresh patch with
> changes squashed together or new commits appended after first commit in that
> patch. Patch is updated accordingly as fresh patch.

(just on mechanics, not on the contents of your actual patch)

You can and should treat any topic that is not yet in 'next' as if it did not exist. If you refined based on a v1 patch, pretend as if you were a perfect developer and you came up with that refined version without producing any problematic things that were pointed ont in your v1. Pretend mistakes in v1 never happened. Pretend that you are perfect! ;-)

If you can limit the signs that an earlier rounds ever existed to

(1) The In-reply-to: header of the message you send your updated
    version of the patch in, so that people can find the older
    version and its discussion thread, and

(2) The cover letter that describes what you improved in the
    updated version relative to the last round, in addition to the
    overview of the series [note: this only exists for a larger
    patch series, and not usually done for a single patch]

you achieved your goal.