On Wed, May 23, 2012 at 04:43:34PM -0500, H Hartley Sweeten wrote: > On Wednesday, May 23, 2012 2:44 PM, Dan Carpenter wrote: > > Hartley, you're doing a great job with all these patches, but it's > > going to be weeks before the merge window closes. We're going to > > end up getting confused with all the patches floating around. > > > > Do you think you could maybe put up a git tree with the current > > stuff so people know when they're stepping on each other's toes? > > I would but really don't know how/were to put one. > I can't speak for Greg but probably he'd still end up taking patches from the list, not from the git tree. So that makes it less of a big deal where you put it, since we'd only use it to just track which patches are out there. So if someone submits a patch to comedi, we'd tell them, "Uh. This conflicts with some previously submitted patches. Please pull from Hartley's tree and modify it so it applies." There are several free git hosting projects out there. I use http://repo.or.cz/ for Smatch. > Also, I'm still a bit of a newbie with git. I would need some help > initially to make sure I didn't screw it up. ;-) Register a project. Do a fork of http://repo.or.cz/w/linux-2.6.git Push Greg's stuff. Go through the email list and download all the comedi patches which Greg doesn't have (raw emails including headers and everything). cat email.txt | git am -s If it doesn't apply complain to the submitter. Don't fix anyone's patches or changelogs. Just complain and make them do the work. Make sure when you apply a patch that the authorship information is preserved. git push ssh://yourname@xxxxxxxxxx/srv/git/project.git master regards, dan carpenter _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
