Ok.

P.S. perhaps somebody will implements a fix... perhaps.

On Thu, Aug 19, 2010 at 3:30 PM, Frans Bouma <[email protected]> wrote:

> > about this " it ends up with you talking me down in some form or the
> other"
> > I don't know what you are talking about.
>
>         To help you, think REALLY HARD about the following:
> Why did you reply with 3 emails to my post, only replying on my first
> sentence, as if I would imply anything with it instead of exactly what I
> said. Why did you think that of me?
>
>        For the record, the only one who replied with any real info to the
> topicstarter was... who? I really don't know why you had to do this, I
> really don't.
>
>                FB
>
> > For others matter: Ok.
> >
> >
> > On Thu, Aug 19, 2010 at 2:00 PM, Frans Bouma <[email protected]> wrote:
> >
> >
> >       > I saw that you tried to be helpful in the other part of your
> mail.
> >
> >
> >              I tried to be helpful in EVERY email here and on nhusers,
> and
> > I
> >       didn't want to imply *anything* in the 1st sentence I wrote. WTF is
> > your
> >       problem?
> >
> >
> >       > What we have notice is that there is a kind of "personal
> questions"
> > when
> >       we
> >       > are talking about our linq-provider and we don't have a
> > "personalized
> >       > customer service" (at least not for free).
> >
> >
> >              I have no idea what you mean/refer to.
> >
> >
> >       > Steve is part of NH's team and the Linq provider is part of
> > NHibernate
> >       core.
> >       > As any other issue, even the issues related to linq-provider are
> > solved by
> >       > the team.
> >       >
> >       > Perhaps, with his silence, Steve and the team altogether are
> trying
> > to say
> >       > the same.
> >
> >
> >              Sorry but I have no idea what you mean, but anyway, it's
> been
> >       enough. Every f*cking time 'Linq' is mentioned and I reply in some
> > form or
> >       another, it ends up with you talking me down in some form or the
> > other. I
> >       just try to be helpful, but I don't need this kind of bickering. If
> > helping
> >       out time after time ends up with some form of bickering, I won't
> > spend my
> >       time on it anymore. Like I've said to Steve before, he can email me
> > any time
> >       with questions about Linq and how to do things, but I won't reply
> to
> > linq
> >       crap here again, as apparently you don't want my help/information
> > about how
> >       to deal with linq expressions and what to expect. In case you don't
> > know,
> >       mr. Maulo, that info is no-where to be found on the net nor in MS'
> >       documentation. Only the small group on this planet who have dealt
> > with these
> >       miserable issues before know what to expect and where a solution
> > 'might' be
> >       found (as the only team who managed to get it all right is the Linq
> > to Sql
> >       team (now abandoned) and they didn't publish any of their info).
> >
> >                      FB
> >
> >       >
> >       > P.S. I'm a "little bit" more loquacious in some cases
> >       >
> >       >
> >       > On Thu, Aug 19, 2010 at 11:54 AM, Frans Bouma <[email protected]>
> wrote:
> >       >
> >       >
> >       >       > On Thu, Aug 19, 2010 at 7:20 AM, Frans Bouma <
> [email protected]>
> > wrote:
> >       >       >
> >       >       >       I don't know if Steve's still reading this list,
> >       >       >
> >       >       > What do you mean ?
> >       >
> >       >
> >       >              Well, I asked in some other linq thread a couple of
> > questions
> >       > to
> >       >       Steve, gave info about how to do things, but never got a
> > reply (was
> >       > in June
> >       >       or so), also all other linq related material is not
> answered
> > by him,
> >       > so I
> >       >       wondered if he was still reading this list. I don't know
> how
> > else to
> >       >       interpret this remark, to be honest.
> >       >
> >       >              But that aside, sorry I tried to be helpful, mr.
> > Maulo.
> >       >
> >       >                      FB
> >       >
> >       >
> >       >
> >       >
> >       >
> >       >
> >       >
> >       >
> >       > --
> >       > Fabio Maulo
> >       >
> >
> >
> >
> >
> >
> >
> >
> > --
> > Fabio Maulo
> >
>
>
>


-- 
Fabio Maulo

Reply via email to