[Haifux] [W2L] Call for lecturer + "Linux guru"

[Doron Tal]

I tend to agree that git is somewhat complex for the novice. It takes awhile
before one feels comfortable working with git. SCMs in general, are not
considered
"core" learning material, so most student will prefer to avoid "wasting"
their
time to earn the required expertise.

Having said that, for the experienced git users, there is not reason to lose
their work, even in the case of some mistake.
For example, most problems can be recovered using:
http://www.kernel.org/pub/software/scm/git/docs/user-manual.html#recovering-lost-changes

Another, less powerful tool, but good enough for immediate disaster recovery
is the ORIG_HEAD reference.

--doron

On Thu, Oct 15, 2009 at 11:38 PM, guy keren <choo at actcom.co.il> wrote:

>
> the problem with git, is that it's very easy to shoot yourself in the
> foot. giving it to students, who might accidentally reset their
> repository into losing their code, is not a very good idea, if you don't
> have time to give a proper explanation plus warnings.
>
> --guy
>
> Tzafrir Cohen wrote:
> > On Thu, Oct 15, 2009 at 09:13:58PM +0200, Eli Billauer wrote:
> >> OK, I think this is a good time to express my view regarding the
> >> "Development tools" lecture. It's purpose, as I see it, is to give the
> >> students a nice start with the "right" tools for developing code, as
> >> needed for their exercises. If their experience is good, they'll stay.
> >> If not, they'll soon use the alternatives.
> >>
> >>
> >> If you want to give a lecture about any other subject, as a
> >> Stay-in-Linux or mainstream lecture, by all means come forward. But
> >> let's try to get some focus on the initial lecture.
> >>
> >>
> >> Correct me if I'm wrong, but a student is not likely to go beyond a
> >> project which runs on a single platform, having a few source files, and
> >> with no more than two or three persons involved. Hence autotools are
> >> irrelevant, and so are version control systems. Tarballing all sources,
> >> and sending to your partner with comments, is as much version control as
> >> you need in these situations.
> >
> > I'm not sure I agree with you regarding version control systems.
> >
> > Specifically distributed version control systems make the common case of
> > a repository for the project simple. Unlike Subversion, you don't need
> > to set up a separate server.
> >
> > And it saves you a whole lot of time in saving ex1.c_1 , ex1.c_2,
> > ex.c.orig and such. I think that demonstarting simple linear workflow
> > (no branches, no remote repositories) with git, bzr or hg could be handy.
> >
>
> _______________________________________________
> Haifux mailing list
> Haifux at haifux.org
> http://hamakor.org.il/cgi-bin/mailman/listinfo/haifux
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://haifux.org/pipermail/haifux/attachments/20091016/1096c4d7/attachment.html