From: "Philip Oakley" <philipoakley@iee.org>
To: "Enrico Weigelt" <enrico.weigelt@vnc.biz>
Cc: "Git List" <git@vger.kernel.org>, "Josef Wolf" <jw@raven.inka.de>
Subject: Re: Workflow for templates?
Date: Sat, 10 Nov 2012 13:44:53 -0000 [thread overview]
Message-ID: <E2479326E6B94EFEAEE8816FD926F36F@PhilipOakley> (raw)
In-Reply-To: 7f1bbe94-b3f6-4728-960d-19e89e8e4166@zcs
From: "Enrico Weigelt" <enrico.weigelt@vnc.biz> Sent: Saturday, November
10, 2012 10:29 AM
>> This is often the key point that requires the 'new mindset'. Most
>> folk
>> use/used the directory heirarchy (subtle distinction with the .git
>> 'repo' directory heirarchy to be noted) as a way of separating
>> ownership
>> between groups. They find it very hard to undo the old mindset and
>> use
>> branches _instead of_ directories for the different group
>> configurations.
>
> hmm, is this really a psychological issue ?
Oh absolutely. It is very very hard to unlearn stuff, especially bad
habits that have had to become ingrained to make them work adequately!
It's like re-learning an alternative to a well loved mnemonic. "CLAP".
>
> well, many years ago, i've seen a talk about git (maybe by linus
> himself),
> which started with something like "forget everything you know abozt
> scm" ...
Most folk don't know why the old way used to be right, and is now so
wrong, so they can't rationalize the change. Hence find the change very
difficult.
[Other than git..] Current SCM methods were established before the
Titanic sank and are based on drawing office practice, and were
transfered and applied to code printouts (which are simply machining
instructions to a compiler). The modern zero cost replication of
"Master" drawings/code printouts has destroyed the original reasons for
the old practices (protect the aluable unique master). Similarly the new
paradigm of "how can I verify that this is a proper copy of the master"
isn't understood.
Definately a psychological issue when your whole world is being turned
upside down ;-)
prev parent reply other threads:[~2012-11-10 13:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-25 21:15 Workflow for templates? Josef Wolf
2012-10-27 18:45 ` Enrico Weigelt
2012-10-31 10:44 ` Josef Wolf
2012-11-06 19:50 ` Josef Wolf
2012-11-06 20:21 ` Pyeron, Jason J CTR (US)
2012-11-06 21:07 ` Josef Wolf
2012-11-07 16:03 ` Holger Hellmuth (IKS)
2012-11-10 7:27 ` Enrico Weigelt
2012-11-10 7:13 ` Enrico Weigelt
2012-11-10 9:56 ` Philip Oakley
2012-11-10 10:29 ` Enrico Weigelt
2012-11-10 13:44 ` Philip Oakley [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E2479326E6B94EFEAEE8816FD926F36F@PhilipOakley \
--to=philipoakley@iee.org \
--cc=enrico.weigelt@vnc.biz \
--cc=git@vger.kernel.org \
--cc=jw@raven.inka.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).