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
Subject: Re: Git User's Survey 2008 partial summary, part 5 - other SCM
Date: Sun, 14 Sep 2008 17:45:06 +0700	[thread overview]
Message-ID: <fcaeb9bf0809140345n11d41430ma9b4096c66776b0c@mail.gmail.com> (raw)
In-Reply-To: <200809112214.18366.jnareb@gmail.com>

On 9/12/08, Jakub Narebski <jnareb@gmail.com> wrote:
>  15) Do you miss features in git that you know from other SCMs?
>     If yes, what features are these (and from which SCM)?
>     (Open ended text - Essay)
>
>  Total respondents       1046 (some/many of them wrote 'no')
>  skipped this question   1249
>
>  This is just a very quick summary, based on a first few pages of
>  responses, Full analysis is I think best left for after closing the
>  survey, because I think this would be a lot of work...
>
>  So here is preliminary list, or rather beginning of one:
>   * sparse/partial checkout and clone (e.g. Perforce)

Have not read the survey result, but do you recall what is the most
used term for sparse/partial checkout? What SCMs do sparse/partial
checkout? I think it could be usable as it is now in my
will-be-sent-again series, but I don't really know how people want it
to from that.
-- 
Duy

  parent reply	other threads:[~2008-09-14 10:46 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-03 14:07 Git User's Survey 2008 partial summary Jakub Narebski
2008-09-03 14:45 ` Shawn O. Pearce
2008-09-03 15:20   ` H.Merijn Brand
2008-09-03 16:25     ` Felipe Contreras
2008-09-04  2:43       ` David Aguilar
2008-09-05 22:17         ` Jan Hudec
2008-09-06  4:17           ` David Aguilar
2008-09-03 15:00 ` David Brown
2008-09-03 15:41 ` Scott Chacon
2008-09-03 16:00   ` Jakub Narebski
2008-09-04 13:23 ` Git User's Survey 2008 partial summary, part 2 Jakub Narebski
2008-09-06  2:22 ` Git User's Survey 2008 partial summary, part 3 Jakub Narebski
2008-09-06  5:15   ` Shawn O. Pearce
2008-09-06  8:27     ` Andreas Ericsson
2008-09-07 23:07     ` Jonas Fonseca
2008-09-07 23:47       ` Shawn O. Pearce
2008-09-06 22:17 ` Git User's Survey 2008 partial summary, part 4 - how do we use Git Jakub Narebski
2008-09-07  8:31   ` Andreas Ericsson
2008-09-07  8:44     ` Jakub Narebski
2008-09-11 20:14 ` Git User's Survey 2008 partial summary, part 5 - other SCM Jakub Narebski
2008-09-11 21:03   ` Anatol Pomozov
     [not found]     ` <48C98F92.40903@workspacewhiz.com>
2008-09-11 22:05       ` Jakub Narebski
2008-09-11 21:54   ` Jeff King
2008-09-11 22:51   ` david
2008-09-12 10:44     ` Jakub Narebski
2008-09-13 21:11       ` david
2008-09-13 22:03         ` Jakub Narebski
2008-09-15 11:51       ` Mark Brown
2008-09-14 10:45   ` Nguyen Thai Ngoc Duy [this message]
2008-09-14 13:32     ` Jakub Narebski
2008-09-15  3:39     ` david
2008-09-15  7:00       ` Andreas Ericsson
2008-09-16 17:12       ` Jakub Narebski
  -- strict thread matches above, loose matches on Subject: below --
2008-09-12 11:11 dhruva

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=fcaeb9bf0809140345n11d41430ma9b4096c66776b0c@mail.gmail.com \
    --to=pclouds@gmail.com \
    --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).