On 24 May 2016 at 06:50, David Sterba <dste...@suse.cz> wrote: > On Mon, May 23, 2016 at 02:26:46PM -0400, Nicholas D Steeves wrote: >> On 23 May 2016 at 13:01, David Sterba <dste...@suse.cz> wrote: >> > On Thu, May 19, 2016 at 09:30:49PM -0400, Nicholas D Steeves wrote: >> >> Sorry for the noise. Please disregard my v1 patch and subsequent >> >> emails. This patch is for upstream linux-next. From now on I think >> >> that's what I'm going to work from, to keep things simple, because it >> >> seems I'm still inept with git. >> > >> > The patch applies cleanly on top of the current branch that's going to >> > Linus tree, so I'll queue it for the next pull request. All your inline >> > notices were addressed. Thanks. >> >> You're welcome, and thank you for the assistance. I don't want to >> annoy everyone with a regular stream of these patches, so what do you >> think of the the following?: I'll submit a patch for user-facing >> typos in btrfs-progs when I find one, > > Sending typo fixes for all user visible text is OK and welcome anytime. > >> if I find any, and a strings & >> comments review for both -progs and kernel twice a year, where one >> review is part of preparing for an LTS kernel. > > Typos in comments can be done once in a year I think.
Thank you for the clarification. When would be the best time? While preparing for an LTS kernel, or a certain amount of time before one? Would you like me to skip 4.10 this year and stick to doing it in the month of May? Best regards, Nicholas -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
