On Thu, Aug 1, 2013 at 8:19 AM, Dave Chinner <david@xxxxxxxxxxxxx> wrote: > On Wed, Jul 31, 2013 at 08:48:40AM +0200, Sedat Dilek wrote: >> On Wed, Jul 31, 2013 at 6:15 AM, Dave Chinner <david@xxxxxxxxxxxxx> wrote: >> > Hi folks, >> > >> > This series of patches is against the curent mmotm tree here: >> > >> > http://git.cmpxchg.org/cgit/linux-mmotm.git/ >> > >> >> "Current" is not precise enough... above tree has git-tags. > > It's most certainly precise. "current" always means the master > branch at the time the series was posted. I.e. same definition as > "top of tree".... > Today, I see in my inbox "mmotm 2013-07-31-16-52 uploaded" which means "master" will change (or has changed). Think of all the people being on vacation and reading your email later. People waste their time if they don't know on what a patchset is based on. Pointing to the git-tag does not hurt. >> As I am not a linux-fs expert I can try to test, preferably against a >> Linux-next release. >> Would you like to test against "vanilla" mmotm or is Linux-next >> suitable in your eyes? > > mmotm is based on the linux-next tree at the time the tree was made. > No, linux-next includes patches from Andrew's mmotm marked in his series file. So, your patches can fit or not, that's why I asked. [1] http://ozlabs.org/~akpm/mmotm/series [2] http://ozlabs.org/~akpm/mmotm/mmotm-readme.txt >> I have seen some typos... are you interested in such feedback? > > feel free to point them out. > Cannot promise anything. Dealing with some embedded stuff. - Sedat - > Cheers, > > Dave. > -- > Dave Chinner > david@xxxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
