On Thu, 5 Jun 2008, Johannes Schindelin wrote: > On Thu, 5 Jun 2008, Boyd Lynn Gerber wrote: > > I have attached the patches necessary to use GIT on some Non Linux OS's. > > One might think that you could now use Git to generate the patches, and > follow the conventions to submit them... I should have. I am just now cloning the git tree. Once I get a my clone I will create a working copy and make the patches to it. > For example, reviewing attached patches makes it unduly hard on the > reviewers. > > For example, you do not have any explanation AKA commit message. > > For example, you use context diffs. > > See Documentation/SubmittingPatches for more hints how to get your > patches integrated. I just found on the website the proper way to submit patches. I will follow it. I just have been submitting patches to to many differt version control systems. I have to submit patches to cvs, svn, hg and git. I have a hard time remembering which source tree is what. I have just now created my /master/src/cvs /master/src/git /master/src/hg /master/src/svn /working/src/cvs /working/src/git /working/src/hg /working/src/svn I am moving things to these directories. This will allow me to know which tools to use for each type of version control. I also still have SCCS and RCS repos as well. I really wish we could get the industry to standardize on git. But that will be a while. Sorry, I did not follow the proper method, for submittal. I did not even know there was one when I submitted the patches. I will do them that way once I finish my migration above. -- Boyd Gerber <gerberb@xxxxxxxxx> ZENEZ 1042 East Fort Union #135, Midvale Utah 84047 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
