On Tue, Feb 07, 2023 at 01:49:15PM +0530, Deepak R Varma wrote: > On Tue, Feb 07, 2023 at 08:25:57AM +0100, Guru Mehar Rachaputi wrote: > > On Mon, Feb 06, 2023 at 10:43:56AM +0100, Greg Kroah-Hartman wrote: > > > On Mon, Feb 06, 2023 at 12:39:08AM +0100, Guru Mehar Rachaputi wrote: > > > good luck! > > > > > > greg k-h > > > > Thanks for taking time. > > > > If my understanding is correct, every version of the patch should > > include all the patches/patchfiles and it should explain what happened in each > > version(in decrement order) through a coverletter. Please correct me otherwise. > > Hi Guru, > Other than the cover letter, each individual patch should also include the patch > version history in the descending order. If a specific patch(es) that is/are > part of a patch-set, did not have any change, we should still increment its > version and record "none" as the change in current version for such patches. > > However, from the patch-set, any patches that are acked, do not need to be > resent along with other patches that are still under revision. But do mentioned > about such accepted/acked patches in the cover letter. > > Hope this helps. > > Thanks, > deepak. > > > > > I do refer "first patch submission" and above is my current > > understanding. > > > > -- > > Thanks & Regards, > > Guru > > > > Hej Deepak, I have a problem in sending patchset through mutt. I have been trying sending to my own mail address but it won't work. When sending patchset I think we should use "In-Reply-To" flag and include "Message-ID" to which we want this to be in series to. I tried both "git send-email" feature and mutt "forwarding feature". Another issue is, how to attach patch file from inside mutt(for example: "mutt -H x.patch" from command line is used to extract header and body of a mail in mutt)? -- Thanks & Regards, Guru
