From: Jakub Narebski <jnareb@gmail.com>
To: Yann Dirson <dirson@bertin.fr>
Cc: git@vger.kernel.org,
Felipe Contreras <felipe.contreras@gmail.com>,
Jakub Narebski <jnareb@gmail.com>
Subject: Re: Git Survey 2011; now let's not forget the index/cache/stage
Date: Wed, 22 Sep 2010 09:38:31 -0700 (PDT) [thread overview]
Message-ID: <m3tylhhgyz.fsf@localhost.localdomain> (raw)
In-Reply-To: <20100921111344.647453d8@chalon.bertin.fr>
Yann Dirson <dirson@bertin.fr> writes:
> > > You agreed it would be there, and it's not, so I wonder what's the
> > > point of asking for feedback if it's going to be forgotten. Next time
> > > I think you should send the final version for review before
> > > publishing.
> >
> > There were two issues conflated that contributed to this error
> > of mine.
> >
> > First, I have re-checked *direct email* responses to request for
> > feedback on Git User's Survey 2010 questions proposal, but I have
> > forgot to re-check responses which were send only to git mailing list
> > without Cc (i.e. in my case *newsgroup* responses). I am very sorry
> > for that.
>
> Well, all that seems to call for a git-backed survey engine, so that
> suggestions could be straightforward patches !
While it could be quite straighforward to design survey engine which
uses git as backend for storing survey schema (the structure of
survey, including questions and choices), I don't think that git as
backend would work for storing answers, if it were to be possible to
(re)edit own answers.
And of course there is problem with *hosting* a survey app...
--
Jakub Narebski
Poland
ShadeHawk on #git
prev parent reply other threads:[~2010-09-22 16:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTi=Fp89-MuYVCNFtSA25hVufbQD5TCJL-ATUDCDH@mail.gmail.com>
2010-09-20 13:38 ` Git Survey 2011; now let's not forget the index/cache/stage Jakub Narebski
2010-09-20 23:28 ` Felipe Contreras
2010-09-21 3:27 ` Jakub Narebski
2010-09-21 9:13 ` Yann Dirson
2010-09-22 16:38 ` Jakub Narebski [this message]
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=m3tylhhgyz.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=dirson@bertin.fr \
--cc=felipe.contreras@gmail.com \
--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.
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).