I've found people often struggle with when and how to rebase in various forms. It could probably use a good portion of time.
On Tue, Dec 1, 2015 at 11:38 AM, Louis Kowolowski <[email protected]> wrote: > > > On Nov 30, 2015, at 10:56 PM, Michael Dexter <[email protected]> > wrote: > > > > On 11/30/15 10:52 PM, Ali Corbin wrote: > >> I don't think I could come up with anything very organized, but I've > used > >> git and github for years and could probably babble on about them. > >> > >> But maybe everyone already groks git and just wants to get up to speed > on > >> github? The only thing it really adds to git is this forking business I > >> think. Except maybe for the wiki and the defect tracking that they give > >> you, and the webpages. > > > > How about... > > > > You create a simple project "foo" on your GitHub account and walk people > > through checking it out, modifying it, committing back, forking it, > > borking it and you follow along on-screen via GitHub.org? > > > If that doesn’t include merge, add that to the list. I’d say something > about git terminology, but @bcantrill already covered it quite nicely on > the recent BSDnow podcast. > > -- > Louis Kowolowski [email protected] > <mailto:[email protected]> > Cryptomonkeys: > http://www.cryptomonkeys.com/ <http://www.cryptomonkeys.com/> > > Making life more interesting for people since 1977 > > > _______________________________________________ > PLUG mailing list > [email protected] > http://lists.pdxlinux.org/mailman/listinfo/plug > > _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
