git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Matthias Andree" <matthias.andree@gmx.de>
To: "Nanako Shiraishi" <nanako3@lavabit.com>
Cc: "Junio C Hamano" <gitster@pobox.com>,
	"Tim Olsen" <tim@brooklynpenguin.com>,
	git@vger.kernel.org
Subject: Re: still getting 'It is a submodule!" in 1.6.2.5
Date: Wed, 06 May 2009 11:57:46 +0200	[thread overview]
Message-ID: <op.uth5yiis1e62zd@balu> (raw)
In-Reply-To: <20090506180925.6117@nanako3.lavabit.com>

Am 06.05.2009, 11:09 Uhr, schrieb Nanako Shiraishi <nanako3@lavabit.com>:

> Quoting "Matthias Andree" <matthias.andree@gmx.de> writes:
>
>> Is there an easy-to-find and easy-to-grasp table that lists which
>> branches  are recommended for which target group? If there is, I have
>> constantly  missed it.
>
> After each major release Junio sends out a message with a title "Note  
> from the maintainer" (or sth like that).

OK.

>> May I suggest that there be a remark on the download page of
>> git-scm.com  that "master" is really the recommended branch?
>
> I'm afraid you are suggesting to a wrong person; Junio doesn't control  
> what's in that domain.

This was in the hopes that the site maintainer was reading this list, and  
given there's a redirection from git.or.cz to the new site, I deemed it  
was somehow semi-official. At least, git-scm.com is concise :-)

-- 
Matthias Andree

      parent reply	other threads:[~2009-05-06  9:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-04 20:39 still getting 'It is a submodule!" in 1.6.2.5 Tim Olsen
2009-05-05  6:43 ` Junio C Hamano
2009-05-05 14:23   ` Tim Olsen
2009-05-05 15:23     ` Tim Olsen
2009-05-06  7:31   ` Matthias Andree
     [not found]     ` <20090506180925.6117@nanako3.lavabit.com>
2009-05-06  9:57       ` Matthias Andree [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=op.uth5yiis1e62zd@balu \
    --to=matthias.andree@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=nanako3@lavabit.com \
    --cc=tim@brooklynpenguin.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).