git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felipe Contreras <felipe.contreras@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jakub Narebski <jnareb@gmail.com>, git@vger.kernel.org
Subject: Re: [RFC] Git User's Survey 2009 - second trial run, and question  about announcing it
Date: Sun, 5 Jul 2009 22:15:54 +0300	[thread overview]
Message-ID: <94a0d4530907051215h755f634bkfd043d88289df29e@mail.gmail.com> (raw)
In-Reply-To: <7vprcfj83z.fsf@alter.siamese.dyndns.org>

On Sun, Jul 5, 2009 at 9:30 PM, Junio C Hamano<gitster@pobox.com> wrote:
> Felipe Contreras <felipe.contreras@gmail.com> writes:
>
>> I guess Junio's blog is the most official one ATM,...
>
> Sorry, don't.
>
>  - Even if you are pretending to be a git community member, you are merely
>   a phoney if you are not reading it.
>
>  - If you want to be up-to-date with what is happening in the community,
>   you should be reading it.  Any important announcement always will
>   appear there.
>
> That would be an official blog.  I do not use mine that way, and nobody
> has to follow it in order to function better in the git land.
>
> It's like expecting Linus to announce the kernel release in his blog.
>
> Not going to happen.  The official channel of this community has always
> been this list.
>
> I'm OK if somebody declares that he will use his blog to relay important
> announcements from this list, to help blog minded people to follow it
> instead of reading the list.
>
> But that won't be me.

I know there's no official git blog, I've tried to change that, but so
far that hasn't happened. IMHO for now the most popular git blog(s)
should announce the survey, I'll announce it at gitlog.wordpress.com
but it is far from being popular.

I understand your position for not making your personal blog the
official one; I wouldn't do that on my personal blog either
(felipec.wordpress.com) that's why I created a separate blog for that,
where you, or anyone else, can do official git posts instead of on
their personal blog.

Cheers.

-- 
Felipe Contreras

  reply	other threads:[~2009-07-05 19:16 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-02 23:30 [RFC] Git User's Survey 2009 - second trial run, and question about announcing it Jakub Narebski
2009-07-03  0:22 ` Junio C Hamano
2009-07-03 22:23   ` Jakub Narebski
2009-07-03 23:19 ` Felipe Contreras
2009-07-04  1:26   ` David Aguilar
2009-07-04  8:24     ` Felipe Contreras
2009-07-04 22:43       ` Jakub Narebski
2009-07-04 23:46         ` Felipe Contreras
2009-07-04 22:40   ` Jakub Narebski
2009-07-04 23:53     ` Felipe Contreras
2009-07-05 17:53       ` Jakub Narebski
2009-07-05 18:30       ` Junio C Hamano
2009-07-05 19:15         ` Felipe Contreras [this message]
2009-07-05 19:45           ` Jakub Narebski
2009-07-05 20:12             ` Felipe Contreras
2009-07-06  8:14               ` Andreas Ericsson
2009-07-06 11:16                 ` Jakub Narebski
2009-07-06 12:31                 ` Felipe Contreras
2009-07-06 13:14                   ` Andreas Ericsson
2009-07-06 21:49             ` Elijah Newren
2009-07-04  9:05 ` Martin Renold
2009-07-06 21:44   ` Jakub Narebski
     [not found] ` <40aa078e0907071716k40d6ce9cwc0f9801f4042ef3a@mail.gmail.com>
2009-07-08  1:02   ` Jakub Narebski

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=94a0d4530907051215h755f634bkfd043d88289df29e@mail.gmail.com \
    --to=felipe.contreras@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --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).