From: Tilman Schmidt <tilman@imap.cc>
To: Brandon Casey <casey@nrlssc.navy.mil>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Jakub Narebski <jnareb@gmail.com>,
git@vger.kernel.org
Subject: Re: The 8th airing of the msysGit herald
Date: Thu, 06 Mar 2008 00:12:26 +0100 [thread overview]
Message-ID: <47CF28DA.9030209@imap.cc> (raw)
In-Reply-To: <47CC47EE.9060004@nrlssc.navy.mil>
[-- Attachment #1: Type: text/plain, Size: 1469 bytes --]
Am 03.03.2008 19:48 schrieb Brandon Casey:
> I think the assumption made was that you were already getting some work
> done with the version of git that you had.
True.
> If you do not yet have a comfortable grasp of git usage
True, too.
> I would suggest the following steps:
>
> 1) Grab "a" version of git (preferably latest stable version)
> -If you need to compile it, read the "INSTALL" file.
> 2) Read intro/tutorials
> -tutorial.txt
> -everyday.txt
> -user-manual.txt (more in-depth)
> These three are mentioned in the git man page.
> 3) Start using it
> -refer to man pages to answer questions as you
> encounter issues
> -ask the mailing list when man pages or other docs
> are unable to answer your questions
Got as far as that. In fact, I'm talking about one specific aspect
of that last substep. (let's call it 3.2)
> 4) End of story
I can't see that yet.
> Upgrading, reading RelNotes, using new features, and reading the high-volume
> mailing list are not required, so it is wrong to suggest that they are barriers
> to entry for using git.
I never meant to suggest that. They only are barriers for proceeding
to step 3.2 and onwards to step 4.
Hope that clears it up a bit.
--
Tilman Schmidt E-Mail: tilman@imap.cc
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Ungeöffnet mindestens haltbar bis: (siehe Rückseite)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 253 bytes --]
next prev parent reply other threads:[~2008-03-05 23:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-02 23:30 The 8th airing of the msysGit herald Johannes Schindelin
2008-03-03 0:44 ` Jakub Narebski
2008-03-03 0:54 ` Johannes Schindelin
2008-03-03 1:10 ` Jakub Narebski
2008-03-03 12:00 ` Tilman Schmidt
2008-03-03 12:05 ` Johannes Schindelin
2008-03-03 18:21 ` Tilman Schmidt
2008-03-03 18:48 ` Brandon Casey
2008-03-05 23:12 ` Tilman Schmidt [this message]
2008-03-03 17:18 ` Junio C Hamano
2008-03-03 18:27 ` Tilman Schmidt
2008-03-03 22:37 ` Junio C Hamano
2008-03-03 22:58 ` Martin Langhoff
2008-03-05 23:40 ` Tilman Schmidt
2008-03-06 0:26 ` Johannes Schindelin
2008-03-06 0:41 ` Junio C Hamano
2008-03-06 2:03 ` Jim Raden
2008-03-06 2:29 ` Johannes Schindelin
2008-03-06 2:42 ` Jim Raden
2008-03-06 4:32 ` [msysGit] " Jay Soffian
2008-03-06 4:33 ` Jim Raden
2008-03-06 11:40 ` [msysGit] " Paul Franz
2008-03-06 4:29 ` Jay Soffian
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47CF28DA.9030209@imap.cc \
--to=tilman@imap.cc \
--cc=Johannes.Schindelin@gmx.de \
--cc=casey@nrlssc.navy.mil \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
/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.
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 NNTP newsgroup(s).