git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tilman Schmidt <tilman@imap.cc>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Jakub Narebski <jnareb@gmail.com>, git@vger.kernel.org
Subject: Re: The 8th airing of the msysGit herald
Date: Mon, 03 Mar 2008 19:21:18 +0100	[thread overview]
Message-ID: <47CC419E.7030704@imap.cc> (raw)
In-Reply-To: <alpine.LSU.1.00.0803031205170.22527@racer.site>

[-- Attachment #1: Type: text/plain, Size: 1342 bytes --]

Am 03.03.2008 13:05 schrieb Johannes Schindelin:
> On Mon, 3 Mar 2008, Tilman Schmidt wrote:
> 
>> Jakub Narebski schrieb:
[...]
>>> For me the sign how incredibly fast the git development is is the fact
>>> that git version from a year ago is considered "ancient".
>> Yes, and that is in itself a problem for people like me who just want to 
>> use git to get some work done. The time I spend installing new git 
>> versions, reading RelNotes and sorting through a rather high-volume 
>> mailing list goes off the time I can spare for working on the Linux 
>> driver I maintain. :-(
> 
> Well, you do not _have_ to upgrade, if you are comfortable with what you 
> have...

True as far as it goes, and for appropriate values of "what I have".
Neither do I _have_ to subscribe to the mailing list, or, for that
matter, to read the release notes of a new version I install.

But git is not particularly easy to learn on my own, so I end up
asking for help. (Arguably this qualifies as "not comfortable with
what I have.") And then "ancient version" translates all too easily
into "you should upgrade to a newer one".

-- 
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 --]

  reply	other threads:[~2008-03-03 18:22 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 [this message]
2008-03-03 18:48             ` Brandon Casey
2008-03-05 23:12               ` Tilman Schmidt
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=47CC419E.7030704@imap.cc \
    --to=tilman@imap.cc \
    --cc=Johannes.Schindelin@gmx.de \
    --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).