git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tilman Schmidt <tilman@imap.cc>
To: Martin Langhoff <martin.langhoff@gmail.com>,
	Junio C Hamano <gitster@pobox.com>
Cc: Jakub Narebski <jnareb@gmail.com>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	msysgit@googlegroups.com, git@vger.kernel.org
Subject: Re: The 8th airing of the msysGit herald
Date: Thu, 06 Mar 2008 00:40:17 +0100	[thread overview]
Message-ID: <47CF2F61.5060208@imap.cc> (raw)
In-Reply-To: <46a038f90803031458t2b404212t10f6e9ae710dc408@mail.gmail.com>

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

Am 03.03.2008 23:58 schrieb Martin Langhoff:
> On Tue, Mar 4, 2008 at 11:37 AM, Junio C Hamano <gitster@pobox.com> wrote:
>>  But if you s/stop/slow down/ what I said, it may start to resemble a more
>>  serious question.

Well, I seriously wouldn't want you to slow down fixing bugs. :-)
Enhancing features is a slightly different matter, because that
tends to impress upon insiders a feeling of "how could we ever have
done without that?" and onwards from there to "how can anybody
seriously without that?" which then easily creates the impression
that the answer to every other question from simple users like me
is "install the newest version, it has a nifty feature that solves
your problem better than anything already present in the version
you have!"

> Given that git dev has such a frantic pace... would it make sense to
> give way to some "version inflation"?
> 
> This would give end users a more clear sense of how much things have
> changed -- a 1.4.x to 1.5.x doesn't seem like much. But a 1.5 to 2.0
> with a "new features summary" will grab a bit of attention, get its
> slashdot article, and be a more frank communication of the work that's
> happened, and what the user can expect.

You've got a point there.

But I'd like to suggest something else still: seeing that my git
mailing list folder has already grown to 363 mails again, of which
probably only a small fraction will concern me as a user - would
it be possible to have separate mailing lists for usage topics and
for discussions of ongoing development? I imagine that might help
those who just want to use git (like me) to find their way around.

Just an idea ...

Thanks,
Tilman

-- 
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-05 23:41 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
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 [this message]
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=47CF2F61.5060208@imap.cc \
    --to=tilman@imap.cc \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jnareb@gmail.com \
    --cc=martin.langhoff@gmail.com \
    --cc=msysgit@googlegroups.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).