On 10 May 2016 at 09:33, David Sterba <[email protected]> wrote: > On Mon, May 09, 2016 at 08:13:29PM -0400, Nicholas D Steeves wrote: >> Trivial fix for typos in comments; I hope this patch isn't a nuisance! > > No, but I don't see the typos in any of the branches (master or the > for-next snapshots).
Sorry, I used for-linus, while following this guide: "git clone git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus" https://btrfs.wiki.kernel.org/index.php/Writing_patch_for_btrfs and "git checkout master" confirms that I'm already on 'master', but "git rebase next" produces the error: fatal: Needed a single revision invalid upstream next I'm very new to git. Should I have cloned the whole linux-btrfs.git without "for-linus"? Am I on the a master branch for the for-linus module, which is separate from the master branch of the main linux-btrfs? On 10 May 2016 at 10:20, David Sterba <[email protected]> wrote: Message-ID: <[email protected]> > On Mon, May 09, 2016 at 08:13:29PM -0400, Nicholas D Steeves wrote: > I ran ispell on the strings from comments, there are like 90+ typos > (attached) that seem worth fixing, if you like. Thank you for the list, I'd be happy to. Are patches against master or next preferred (I don't see a for-next branch)? Kind regards, Nicholas -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
