git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Nguyen Thai Ngoc Duy" <pclouds@gmail.com>
To: "Jakub Narebski" <jnareb@gmail.com>
Cc: git@vger.kernel.org, "Paolo Ciarrocchi" <paolo.ciarrocchi@gmail.com>
Subject: Re: [RFC] Git User's Survey 2007
Date: Mon, 30 Jul 2007 17:25:01 -0400	[thread overview]
Message-ID: <fcaeb9bf0707301425y58b423f6x6141949845483e01@mail.gmail.com> (raw)
In-Reply-To: <200707271320.06313.jnareb@gmail.com>

On 7/27/07, Jakub Narebski <jnareb@gmail.com> wrote:
> It's been more than a year since last Git User's Survey. It would be
> interesting to find what changed since then. Therefore the idea to
> have another survey.

I am probably going a little far here. I think we should include
briefly in the survey announcement what git has achieved since the
last survey. We want to know what changed from users. Maybe users also
want to know what changed from git since then. Also it would be good
advertisement if it gets posted on online magazines and popular sites.

-- 
Duy

  parent reply	other threads:[~2007-07-30 21:25 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-25  1:58 Git User's Survey 2007 Jakub Narebski
2007-07-25 16:19 ` Marco Costalba
2007-07-26  4:52   ` Steven Grimm
2007-07-27 11:20 ` [RFC] " Jakub Narebski
2007-07-27 12:21   ` Nguyen Thai Ngoc Duy
2007-07-27 13:01   ` Andy Parkins
2007-07-27 19:07     ` Jakub Narebski
2007-07-28  8:02       ` Andy Parkins
2007-07-29 16:50   ` Paolo Ciarrocchi
2007-07-29 17:05     ` Paolo Ciarrocchi
2007-07-30  0:21     ` Jakub Narebski
2007-07-30  3:35       ` Shawn O. Pearce
2007-07-30 13:40         ` Jakub Narebski
2007-07-30  7:44       ` Paolo Ciarrocchi
2007-07-30 13:26         ` Jakub Narebski
2007-07-30 19:26         ` David Kastrup
2007-07-30 21:12           ` Junio C Hamano
2007-07-30 21:37           ` Jakub Narebski
2007-07-30 22:38             ` David Kastrup
2007-07-30 21:25   ` Nguyen Thai Ngoc Duy [this message]
2007-07-30 21:35     ` Jakub Narebski
2007-07-30 20:56 ` [RFC (take 2) " Jakub Narebski
2007-07-31  0:32   ` Shawn O. Pearce
2007-07-31  0:45     ` Jakub Narebski
2007-07-31  1:09       ` Shawn O. Pearce
2007-07-31  1:24         ` Junio C Hamano
2007-07-31  1:31           ` Shawn O. Pearce
2007-07-31 11:22   ` Jakub Narebski
2007-07-31 11:33     ` Paolo Ciarrocchi
2007-07-31 12:30       ` Jakub Narebski
2007-07-31 16:35         ` Git User's Survey 2007 - web survey site Jakub Narebski
2007-07-31 19:07           ` Paolo Ciarrocchi
2007-08-02  4:51             ` Martin Langhoff
2007-08-02 13:04               ` Paolo Ciarrocchi
2007-08-04  0:50 ` [RFC (take 3)] Git User's Survey 2007 Jakub Narebski
2007-08-04  5:41   ` Shawn O. Pearce
2007-08-04 12:10     ` Jakub Narebski
2007-08-04  7:40   ` David Kastrup
2007-08-05 20:06     ` Jakub Narebski
2007-08-06  0:29       ` Johannes Schindelin
2007-08-05  9:30   ` Asger Ottar Alstrup
2007-08-06  1:17     ` Jakub Narebski
2007-08-06  5:48       ` Asger Ottar Alstrup
2007-08-06 15:44         ` Jakub Narebski
2007-08-05 20:51 ` [RFC (take 4)] " Jakub Narebski
2007-08-14  1:51 ` [RFC (final)] " Jakub Narebski
  -- strict thread matches above, loose matches on Subject: below --
2007-08-14 22:38 [RFC} " 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=fcaeb9bf0707301425y58b423f6x6141949845483e01@mail.gmail.com \
    --to=pclouds@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --cc=paolo.ciarrocchi@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).