2012/5/30 Richard Sharpe <realrichardsharpe@xxxxxxxxx>: > Hi folks, > > I find it easier to get to know a body of code if I have a specific goal. > > If no one has any objections I would like to work on removing > GlobalMid_Lock (or at least, moving it into struct TCP_Server_Info.) > > Which branch should I work in? I can see: > > master > * smb2-dev > remotes/origin/HEAD -> origin/master > remotes/origin/cifs-patches > remotes/origin/for-next > remotes/origin/master > remotes/origin/smb2-3.4 > remotes/origin/smb2-dev > remotes/origin/smb2-dev-prev > remotes/origin/smb2-dev2 > > or perhaps I should create my own for the moment? > > -- > Regards, > Richard Sharpe > (何以解憂？唯有杜康。--曹操) > -- > To unsubscribe from this list: send the line "unsubscribe linux-cifs" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html Hi! That's good point to start with - no objections from my side. I think you should create your own branch based on Steve's master. As soon as we come to agreement with a change (from any author - yours, Jeff's, etc) it will go to Steve's for-next branch and each of us should rebase his own work branch(es) - from my side they are 'cifs-patches' and 'smb2-dev'. Let the list know about your branch as your create it and if it will be available online, please. P.S. It seems that your remote 'origin' here is my git repo on git.altlinux.ru. You should refetch it often enough if you want to get my latest version (smb2-dev-prev, smb2-dev2, smb2-3.4 no longer exist) > master > * smb2-dev > remotes/origin/HEAD -> origin/master > remotes/origin/cifs-patches > remotes/origin/for-next > remotes/origin/master > remotes/origin/smb2-3.4 > remotes/origin/smb2-dev > remotes/origin/smb2-dev-prev > remotes/origin/smb2-dev2 -- Best regards, Pavel Shilovsky. -- To unsubscribe from this list: send the line "unsubscribe linux-cifs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
