git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Yann Dirson <ydirson@free.fr>
To: git@vger.kernel.org
Subject: Re: [RFC] Git User's Survey 2010 (resend)
Date: Thu, 8 Jul 2010 07:24:34 +0000 (UTC)	[thread overview]
Message-ID: <loom.20100708T091339-404@post.gmane.org> (raw)
In-Reply-To: m3k4p7m0sv.fsf@localhost.localdomain

Jakub Narebski <jnareb <at> gmail.com> writes:
> > > === 12. What kind of Git tools do you use? ===
> > > (multiple choice, with other)
> > [...]
> > >  + graphical blame or pickaxe tool
> > 
> > Mention gitk as example here ?
> 
> You meant here "git gui blame", didn't you?

Well, yes - that comes from the fact I only use the it from gitk :)

> > > === 16. Which of the following features do you use? ===
> > > (multiple choice, with other)
> > [...]
> > >  + one-way interaction with other SCMs (from SCM to git)
> > 
> > One-way from git to other SCM ?  I'm sure we care if many people do that :)
> 
> One way from SCM to git.

No, I was really suggesting to ask whether people work on a remote git repo
using another VCS, much like we do access other VCS' repo using git.  Not sure
whether this survey would reach those users, though.

 
> > + sophisticated diffcore stages (eg. directory rename, indent detection,
> >   content move)
> 
> Thanks.
> 
> BTW. I think wholesame directory rename detection is one of proposed
> features already.

d'oh - how could I miss it :)


> > > What features should be mentioned besides those above?  What criteria
> > > should we have for including features in this list?
> > 
> > Not sure if any reasonable idea that appeared on the list should be
> > left out.  Answers would provide feedback for features not necessarily
> > interesting to the average git <at> vger reader, but still appealing to our
> > users.
> 
> I don't think ideas about _internal_ changes need to be here.  Also,
> I do not remember _every_ feature proposel that appeared on the list...

At some point[1] we had a volunteer secretary willing to take note of bugs.  I
just went to see whether proposed features were tracked as well, but it appears
that initiative has stalled already :(

http://marc.info/?l=git&m=126299754631066&w=4

Best regards,
-- 
Yann

  reply	other threads:[~2010-07-08  7:24 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-03 19:58 [RFC] Git User's Survey 2010 (resend) Jakub Narebski
2010-07-04  0:21 ` Ævar Arnfjörð Bjarmason
2010-07-04  8:13   ` Jakub Narebski
2010-07-07  9:18     ` Yann Dirson
2010-07-07 21:43       ` Jakub Narebski
2010-07-10 11:01   ` Felipe Contreras
2010-07-04  9:07 ` David Bainbridge
2010-07-04 11:14   ` Jakub Narebski
2010-07-04 20:48     ` David Bainbridge
2010-07-05  7:19       ` Jakub Narebski
2010-07-04 22:43 ` Scott Chacon
2010-07-04 23:48   ` Jakub Narebski
2010-07-07 12:28 ` Yann Dirson
2010-07-07 21:37   ` Jakub Narebski
2010-07-08  7:24     ` Yann Dirson [this message]
2010-07-10 11:31 ` Felipe Contreras
2010-07-10 19:58   ` Jakub Narebski
2010-07-11  9:57     ` Felipe Contreras
2010-07-11 17:42       ` Jakub Narebski
2010-07-12 10:14         ` David Bainbridge
2010-07-12 10:19           ` Felipe Contreras
2010-07-12 10:22             ` David Bainbridge
2010-08-09 21:59 ` Felipe Contreras
2010-08-10 22:16   ` 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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=loom.20100708T091339-404@post.gmane.org \
    --to=ydirson@free.fr \
    --cc=git@vger.kernel.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).