On Sat, Jan 10, 2009 at 6:11 AM, Junichi Uekawa wrote: > I am thinking of recommending the users to create a branch ... > and throw away their branches when they are included upstream. Yes, with a patch based workflow, this is almost required; all of the commits will at least have different committer information. There's nothing wrong with this approach. > Something tells me the problem is that I'm probably using a workflow > that resembles SVN too much, and users aren't used to branches yet. > Has anybody found this to be a problem, or better yet, is there a > better workflow? If you need the commits to be identical, and you don't mind your email consisting of a binary blob attachment, you can ask your contributors to send you a bundle instead of a series of patches. "git help bundle" for details. Peter Harris -- 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
