Robert: Well, I'm not advocating at all using all their practices, just the guide for how we want to use Git as a place to start our own process. Or, more accurately, how newbie to Git can use it without "surprises". David's right, I'm really looking at just the commit patches part.
> The thing I want to model most is the form. It's a clear set of steps I can > use to get my feet wet and refine if necessary later. _What_ those steps are > open to change. > I'm getting a little numbed by this endless debate about how to use the shiny > new Git thing. Unless we (well, Git pros) want to coach every one of us > new-to-Git folks individually, a "how to" guide is indicated. So I'm trying > to get something concrete we can then change to suit. As usual, of course, > people are more than generous with their time/advice, but why make more work > for them? > Git is just a tool. Right now, the learning curve is just obstructing my > getting any "real work" done. We can debate how sparse my code contributions > have been recently some other time ;) > There's nothing coercive about this proposal. If people have a favorite way > of making Git stand up and do tricks, I'm not about to ask anyone to change > it. > I have no objections to there being multiple processes outlined in whatever > doc we create, just as long as there's a consistent set of steps outlined > that I can follow for each workflow without parsing endless "if you want > this, then do that" branches. > The very fact that this conversation has lasted so long is all the proof I > need that Git has enough different ways of being used that a "how to" guide > is a good thing. Best, Erick On Tue, Jan 26, 2016 at 8:54 AM, Mark Miller <[email protected]> wrote: > They say the same thing about our horrid build system and so won't learn > from our other good practices. What a stupid way to think on both sides. > > - Mark > > On Tue, Jan 26, 2016 at 11:30 AM, Michael McCandless > <[email protected]> wrote: >> >> On Tue, Jan 26, 2016 at 10:54 AM, [email protected] >> <[email protected]> wrote: >> > Rob, >> > I'll trust your assessment of the technical deficiencies of the Hadoop >> > codebase as I have no experience to say one way or the other. >> >> I will trust Rob's assessment too. >> >> > But I'm >> > confused why this is relevant to wether they have a decent process & >> > docs on >> > how to use git? >> >> Actually I think the relationship is clear? >> >> If XYZ entity creates something scary looking to me, then it's >> appropriate for me to question XYZ's dev practices/processes. I.e. I >> would not want to look for inspiration on dev practices from such an >> XYZ project. >> >> Mike McCandless >> >> http://blog.mikemccandless.com >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > > > -- > - Mark > > http://about.me/markrmiller --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
