From: Jakub Narebski <jnareb@gmail.com>
To: "Nguyen Thai Ngoc Duy" <pclouds@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 15:32:56 +0200 [thread overview]
Message-ID: <200809141532.58164.jnareb@gmail.com> (raw)
In-Reply-To: <fcaeb9bf0809140345n11d41430ma9b4096c66776b0c@mail.gmail.com>
On Sun, 14 Sep 2008, Nguyen Thai Ngoc Duy wrote:
> 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.
Well, I do not remember, and I think I haven't got original data now,
only the above summary. Besides, I haven't even began analysing data
from question 34. about ideas for features, and I guess we would see
'partial checkou' ide there too.
>From short discussion on #git channel, Abhijit Menon-Sen (crab) said
that they are 'restricted views' in Perforce, but this terminology is
completly alien to Git. Bjorn Steinbrink (doener_) mentioned that
Subversion 1.5 acquired something they call 'sparse directories':
http://blogs.open.collab.net/svn/2007/06/sparse-director.html
(Sidenote: perhaps it would be worth to follow SVN UI for sparse
checkout here?). In short, people on #git agreed that 'partial
checkout' is a good name; I think that 'sparse checkout' better renders
idea that one can checkout _set_ of files and directories, and it is
not only limited to single subdirectory ('subtree checkout' /
'subdirectory checkout') or a single file.
Comparison table on Better SCM Initiative
http://better-scm.berlios.de/comparison/comparison.html
names it "Ability to Work only on One Directory of the Repository" and
uses '"work_on_dir"' id.
HTH
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2008-09-14 13:34 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
2008-09-14 13:32 ` Jakub Narebski [this message]
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=200809141532.58164.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=pclouds@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.