Moving to github ? - mockito

The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Message from discussion Moving to github ?
Received-SPF: pass (google.com: domain of brice.duth...@gmail.com designates 209.85.214.45 as permitted sender) client-ip=209.85.214.45;
MIME-Version: 1.0
In-Reply-To: <CAPffK0FwERssW8YCWqFj39LCwy3XAJdC6xczJfneo34cWaR...@mail.gmail.com>
References: <CALTMA7socc7dBEW0W0YvpYxSnnCVT8+03RxLBUyDqQPT7Rz...@mail.gmail.com>
 <ae5147b0-7359-413a-9a0c-7af7ce173...@p8g2000yqa.googlegroups.com>
 <CAJreXKCC5HsXbxgnQff_h_6g0_Yre8JagkQeovJj4+RzxGb...@mail.gmail.com>
 <a989c7ac-a13a-4c40-adbf-854fe1736...@j8g2000yqb.googlegroups.com>
 <CALTMA7t-kx+w6gBjJNpNXb3QXZEMamnUjxo-NPffbj7s+ea...@mail.gmail.com>
 <CAPffK0FdRikFpsiwtx_0cAxbSzt0uma6e_Tmgqxuci1J_7O...@mail.gmail.com>
 <CAJreXKCoMSSemAP_XkFmDPf8DiSY1F8cY4huGXu_YX42-cu...@mail.gmail.com>
 <CALTMA7toacuhvc6_N_kPR3Wxf9o9gJkw+Lrty8rkPzzARUD...@mail.gmail.com> <CAPffK0FwERssW8YCWqFj39LCwy3XAJdC6xczJfneo34cWaR...@mail.gmail.com>
From: Brice Dutheil <brice.duth...@gmail.com>
Date: Tue, 7 Aug 2012 16:43:58 +0200
Message-ID: <CALTMA7t-5CgtRFOZ0gFojNUCuhS+LTGcVGJY0xHGBNNioXZ...@mail.gmail.com>
Subject: Re: [mockito] Re: Moving to github ?
To: mockito@googlegroups.com
Content-Type: multipart/alternative; boundary=0015173fe698af7bb304c6ae08d4

--0015173fe698af7bb304c6ae08d4
Content-Type: text/plain; charset=UTF-8

@Eric What I had in mind is more to avoid the creation of a duplicate issue
on the new tracker, because some user didn't actually take a look at the
older tracker. If all issues are in the same tracker then it's easy to look
up for duplicate issues, even for us.


-- Brice



On Tue, Aug 7, 2012 at 4:37 PM, Eric Lefevre-Ardant <e...@ericlefevre.net>wrote:

> "avoid duplicate issues across trackers"
>
> If they are all closed (which is what I was suggesting), then they are not
> duplicated, right?
>
>
> On 7 August 2012 16:29, Brice Dutheil <brice.duth...@gmail.com> wrote:
>
>> @James Well, from my point of view, git is not as user friendly as
>> mercurial, even if there have been much progress in this area.
>> Some commands do not express the intent from the user perspective, I know
>> it's possible to create aliases, still the user has to create them.
>> I recognise myself the power of git, but I still like the friendliness of
>> mercurial.
>>
>> @Eric I'm not sure about that, I personally would like to have
>> a centralised space, to avoid duplicate issues across trackers. I don't
>> know how the rest of the team feels about that. Anyway the tracker is not a
>> priority for now.
>>
>>
>> -- Brice
>>
>>
>>
>> On Tue, Aug 7, 2012 at 4:14 PM, James Carr <james.r.c...@gmail.com>wrote:
>>
>>> "Everyone will need to get accustomed to git"
>>>
>>> You say that like it's a bad thing. ;)
>>>
>>>
>>> Thanks,
>>> James
>>>
>>>
>>> On Tue, Aug 7, 2012 at 9:12 AM, Eric Lefevre-Ardant
>>> <e...@ericlefevre.net> wrote:
>>> > Regarding old issues: I'd bet that 80% of them will remain unsolved.
>>> >
>>> > I suggest that you migrate only the ones that have had any activity in
>>> the
>>> > last 6 months.
>>> > Then close of them and put a message in the ones > 6 months explaining
>>> that,
>>> > if it is still relevant, then the person should recreate the issue in
>>> > Github.
>>> >
>>> > Eric
>>> >
>>> >
>>> > On 7 August 2012 16:02, Brice Dutheil <brice.duth...@gmail.com> wrote:
>>> >>
>>> >> Hi,
>>> >>
>>> >> Thanks for the feedback.
>>> >>
>>> >> @wel Actually as I said that other resources such as documentation,
>>> wiki,
>>> >> etc will stay *for now*, which means that we don't want to move them
>>> but if
>>> >> the move is relevant and offers more advantages it might happen.
>>> >>
>>> >> Now what I have to say :
>>> >> Github offer actually many more feature than we have on Google Code.
>>> And
>>> >> Google Code doesn't really show any sign of improvements or new
>>> features,
>>> >> while Github is actually doing pretty well in that regard. Bitbucket
>>> is also
>>> >> quite good.
>>> >>
>>> >> Some advantages we can see in Github that Google Code don't have :
>>> >> - Pull request
>>> >> - Code Review : https://github.com/features/projects/codereview
>>> >> - SSH support
>>> >> - better branch comparison :
>>> >>
>>> https://github.com/AxonFramework/AxonFramework/compare/master...axon-1.4.x
>>> >>
>>> >> Plus some interesting gadgets :
>>> >> - Also there is nice tutorials :
>>> >> https://github.com/blog/1183-try-git-in-your-browser
>>> >> - Graphs on the repository :
>>> >> https://github.com/AxonFramework/AxonFramework/graphs
>>> >> - The network graph :
>>> >> https://github.com/blog/39-say-hello-to-the-network-graph-visualizer
>>> >>
>>> >> Things on github we are not yet ready to use, that doesn't mean these
>>> >> features are not great (on github) :
>>> >> - Issues, Wiki, Downloads
>>> >>
>>> >> The bad :
>>> >> - Everyone will need to get accustomed to git
>>> >> - We need to migrate the repository, while it mostly works, there is
>>> some
>>> >> adjustments to do regarding tags name
>>> >> - Everyone who had a googlecode account will need a new one on Github
>>> >>
>>> >> ----------
>>> >>
>>> >> Beyond the scope of that repository change, moving the issue tracker
>>> is
>>> >> bothering us, which is why we don't want to switch right now. Here's
>>> what's
>>> >> bothering us *if* we switch to a new issue management system :
>>> >>   - What happens of the old issues? Shall we keep them, as they are
>>> most
>>> >> likely indexed by Google & co ? If yes shall we close them, and
>>> redirect the
>>> >> issues to the new system ?
>>> >>   - What about the people that followed the issues ?
>>> >>   - Changesets are different between git and mercurial, so automatic
>>> links
>>> >> might become incorrect ("revision 441930b6659a"). Note that we
>>> already have
>>> >> this issue (still un resolved) when the team switched from subversion
>>> to
>>> >> mercurial.
>>> >>   - For the transfer, there is no real import stuff to help the
>>> switch.
>>> >> Youtrack though offer this support.
>>> >>
>>> >> Anyway we are not there yet.
>>> >>
>>> >>
>>> >>
>>> >> Cheers,
>>> >> -- Brice
>>> >>
>>> >>
>>> >>
>>> >> On Fri, Aug 3, 2012 at 4:50 PM, welk <kandpwel...@gmail.com> wrote:
>>> >>>
>>> >>> Hey James, good to see you.
>>> >>>
>>> >>> Again, I have never tried to fork Mockito, or offer patches, etc.  So
>>> >>> I don't know that pain, nor can I compare that to Github, but I have
>>> >>> done Googlecode code reviews and I find them very intuitive and
>>> >>> doable.  I also *much* prefer the documentation/wiki and Issues
>>> >>> features on Googlecode (as Brice has suggested they keep those things
>>> >>> here).  Frankly, whenever, I have to navigate thru Github as a casual
>>> >>> user, I am much more frustrated -- especially code browsig.  GC AJAX
>>> >>> tree view is much easier to use.
>>> >>>
>>> >>> But, I again I confess that my use of Mockito has been essentially
>>> >>> confined to source/issue/release/documentation browsing, and not
>>> >>> really anything on team development efforts.  My own googlecode
>>> >>> development project has only had 2 users, no forks, and I have done
>>> >>> 95% of the development.  So my pain points are more limited than
>>> >>> perhaps those who are impacted most by the decision to move or stay.
>>> >>> I really would like to understand more for my own benefit.
>>> >>>
>>> >>> On Aug 2, 2:56 pm, James Carr <james.r.c...@gmail.com> wrote:
>>> >>> > Well, for the most part github is more of a reason in itself to use
>>> >>> > github rather than git. Bitbucket offered git support last year at
>>> >>> > prices cheaper than what we pay github for but we stuck with github
>>> >>> > for a lot of the features, such as code reviews, comments, painless
>>> >>> > forking, etc.
>>> >>> >
>>> >>> > You can contribute to a F/OSS project on github without even
>>> knowing
>>> >>> > git. The barrier to entry is pretty low.
>>> >>> >
>>> >>> > Thanks,
>>> >>> > James
>>> >>>
>>> >>> --
>>> >>> You received this message because you are subscribed to the Google
>>> Groups
>>> >>> "mockito" group.
>>> >>> To post to this group, send email to mockito@googlegroups.com.
>>> >>> To unsubscribe from this group, send email to
>>> >>> mockito+unsubscribe@googlegroups.com.
>>> >>> For more options, visit this group at
>>> >>> http://groups.google.com/group/mockito?hl=en.
>>> >>>
>>> >>
>>> >> --
>>> >> You received this message because you are subscribed to the Google
>>> Groups
>>> >> "mockito" group.
>>> >> To post to this group, send email to mockito@googlegroups.com.
>>> >> To unsubscribe from this group, send email to
>>> >> mockito+unsubscribe@googlegroups.com.
>>> >> For more options, visit this group at
>>> >> http://groups.google.com/group/mockito?hl=en.
>>> >
>>> >
>>> > --
>>> > You received this message because you are subscribed to the Google
>>> Groups
>>> > "mockito" group.
>>> > To post to this group, send email to mockito@googlegroups.com.
>>> > To unsubscribe from this group, send email to
>>> > mockito+unsubscribe@googlegroups.com.
>>> > For more options, visit this group at
>>> > http://groups.google.com/group/mockito?hl=en.
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "mockito" group.
>>> To post to this group, send email to mockito@googlegroups.com.
>>> To unsubscribe from this group, send email to
>>> mockito+unsubscribe@googlegroups.com.
>>> For more options, visit this group at
>>> http://groups.google.com/group/mockito?hl=en.
>>>
>>>
>>  --
>> You received this message because you are subscribed to the Google Groups
>> "mockito" group.
>> To post to this group, send email to mockito@googlegroups.com.
>> To unsubscribe from this group, send email to
>> mockito+unsubscribe@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/mockito?hl=en.
>>
>
>  --
> You received this message because you are subscribed to the Google Groups
> "mockito" group.
> To post to this group, send email to mockito@googlegroups.com.
> To unsubscribe from this group, send email to
> mockito+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/mockito?hl=en.
>

--0015173fe698af7bb304c6ae08d4
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div>@Eric What I had in mind is more to avoid the creation of a duplicate =
issue on the new tracker, because some user didn&#39;t actually take a look=
 at the older tracker. If all issues are in the same tracker then it&#39;s =
easy to look up for duplicate issues, even for us.</div>

<div><br></div><br clear=3D"all"><div>--=C2=A0Brice</div><br>
<br><br><div class=3D"gmail_quote">On Tue, Aug 7, 2012 at 4:37 PM, Eric Lef=
evre-Ardant <span dir=3D"ltr">&lt;<a href=3D"mailto:e...@ericlefevre.net" t=
arget=3D"_blank">e...@ericlefevre.net</a>&gt;</span> wrote:<br><blockquote =
class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid=
;padding-left:1ex">

&quot;<span style=3D"color:rgb(34,34,34);font-size:13px;font-family:arial,s=
ans-serif">avoid duplicate issues across trackers</span>&quot;<div><br></di=
v><div>If they are all closed (which is what I was suggesting), then they a=
re not duplicated, right?<div>

<div class=3D"h5"><br>

<br><div class=3D"gmail_quote">On 7 August 2012 16:29, Brice Dutheil <span =
dir=3D"ltr">&lt;<a href=3D"mailto:brice.duth...@gmail.com" target=3D"_blank=
">brice.duth...@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gma=
il_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-lef=
t:1ex">



@James Well, from my point of view, git is not as user friendly as mercuria=
l, even if there have been much progress in this area.<div>Some commands do=
 not express the intent from the user perspective, I know it&#39;s possible=
 to create aliases, still the user has to create them. I=C2=A0recognise=C2=
=A0myself the power of git, but I still like the friendliness of mercurial.=
</div>





<div><div><br></div><div>@Eric I&#39;m not sure about that, I=C2=A0personal=
ly=C2=A0would like to have a=C2=A0centralised=C2=A0space, to avoid duplicat=
e issues across trackers. I don&#39;t know how the rest of the team feels a=
bout that. Anyway the tracker is not a priority for now.</div>



<span><font color=3D"#888888">

<div><br></div></font></span><div><span><font color=3D"#888888"><br clear=
=3D"all"><div>--=C2=A0Brice</div></font></span><div><div><br>
<br><br><div class=3D"gmail_quote">On Tue, Aug 7, 2012 at 4:14 PM, James Ca=
rr <span dir=3D"ltr">&lt;<a href=3D"mailto:james.r.c...@gmail.com" target=
=3D"_blank">james.r.c...@gmail.com</a>&gt;</span> wrote:<br><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pa=
dding-left:1ex">





<div>&quot;Everyone will need to get accustomed to git&quot;<br>
<br>
</div>You say that like it&#39;s a bad thing. ;)<br>
<br>
<br>
Thanks,<br>
James<br>
<div><div><br>
<br>
On Tue, Aug 7, 2012 at 9:12 AM, Eric Lefevre-Ardant<br>
&lt;<a href=3D"mailto:e...@ericlefevre.net" target=3D"_blank">eric@ericlefe=
vre.net</a>&gt; wrote:<br>
&gt; Regarding old issues: I&#39;d bet that 80% of them will remain unsolve=
d.<br>
&gt;<br>
&gt; I suggest that you migrate only the ones that have had any activity in=
 the<br>
&gt; last 6 months.<br>
&gt; Then close of them and put a message in the ones &gt; 6 months explain=
ing that,<br>
&gt; if it is still relevant, then the person should recreate the issue in<=
br>
&gt; Github.<br>
&gt;<br>
&gt; Eric<br>
&gt;<br>
&gt;<br>
&gt; On 7 August 2012 16:02, Brice Dutheil &lt;<a href=3D"mailto:brice.duth=
e...@gmail.com" target=3D"_blank">brice.duth...@gmail.com</a>&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt; Hi,<br>
&gt;&gt;<br>
&gt;&gt; Thanks for the feedback.<br>
&gt;&gt;<br>
&gt;&gt; @wel Actually as I said that other resources such as documentation=
, wiki,<br>
&gt;&gt; etc will stay *for now*, which means that we don&#39;t want to mov=
e them but if<br>
&gt;&gt; the move is relevant and offers more advantages it might happen.<b=
r>
&gt;&gt;<br>
&gt;&gt; Now what I have to say :<br>
&gt;&gt; Github offer actually many more feature than we have on Google Cod=
e. And<br>
&gt;&gt; Google Code doesn&#39;t really show any sign of improvements or ne=
w features,<br>
&gt;&gt; while Github is actually doing pretty well in that regard. Bitbuck=
et is also<br>
&gt;&gt; quite good.<br>
&gt;&gt;<br>
&gt;&gt; Some advantages we can see in Github that Google Code don&#39;t ha=
ve :<br>
&gt;&gt; - Pull request<br>
&gt;&gt; - Code Review : <a href=3D"https://github.com/features/projects/co=
dereview" target=3D"_blank">https://github.com/features/projects/codereview=
</a><br>
&gt;&gt; - SSH support<br>
&gt;&gt; - better branch comparison :<br>
&gt;&gt; <a href=3D"https://github.com/AxonFramework/AxonFramework/compare/=
master...axon-1.4.x" target=3D"_blank">https://github.com/AxonFramework/Axo=
nFramework/compare/master...axon-1.4.x</a><br>
&gt;&gt;<br>
&gt;&gt; Plus some interesting gadgets :<br>
&gt;&gt; - Also there is nice tutorials :<br>
&gt;&gt; <a href=3D"https://github.com/blog/1183-try-git-in-your-browser" t=
arget=3D"_blank">https://github.com/blog/1183-try-git-in-your-browser</a><b=
r>
&gt;&gt; - Graphs on the repository :<br>
&gt;&gt; <a href=3D"https://github.com/AxonFramework/AxonFramework/graphs" =
target=3D"_blank">https://github.com/AxonFramework/AxonFramework/graphs</a>=
<br>
&gt;&gt; - The network graph :<br>
&gt;&gt; <a href=3D"https://github.com/blog/39-say-hello-to-the-network-gra=
ph-visualizer" target=3D"_blank">https://github.com/blog/39-say-hello-to-th=
e-network-graph-visualizer</a><br>
&gt;&gt;<br>
&gt;&gt; Things on github we are not yet ready to use, that doesn&#39;t mea=
n these<br>
&gt;&gt; features are not great (on github) :<br>
&gt;&gt; - Issues, Wiki, Downloads<br>
&gt;&gt;<br>
&gt;&gt; The bad :<br>
&gt;&gt; - Everyone will need to get accustomed to git<br>
&gt;&gt; - We need to migrate the repository, while it mostly works, there =
is some<br>
&gt;&gt; adjustments to do regarding tags name<br>
&gt;&gt; - Everyone who had a googlecode account will need a new one on Git=
hub<br>
&gt;&gt;<br>
&gt;&gt; ----------<br>
&gt;&gt;<br>
&gt;&gt; Beyond the scope of that repository change, moving the issue track=
er is<br>
&gt;&gt; bothering us, which is why we don&#39;t want to switch right now. =
Here&#39;s what&#39;s<br>
&gt;&gt; bothering us *if* we switch to a new issue management system :<br>
&gt;&gt; =C2=A0 - What happens of the old issues? Shall we keep them, as th=
ey are most<br>
&gt;&gt; likely indexed by Google &amp; co ? If yes shall we close them, an=
d redirect the<br>
&gt;&gt; issues to the new system ?<br>
&gt;&gt; =C2=A0 - What about the people that followed the issues ?<br>
&gt;&gt; =C2=A0 - Changesets are different between git and mercurial, so au=
tomatic links<br>
&gt;&gt; might become incorrect (&quot;revision 441930b6659a&quot;). Note t=
hat we already have<br>
&gt;&gt; this issue (still un resolved) when the team switched from subvers=
ion to<br>
&gt;&gt; mercurial.<br>
&gt;&gt; =C2=A0 - For the transfer, there is no real import stuff to help t=
he switch.<br>
&gt;&gt; Youtrack though offer this support.<br>
&gt;&gt;<br>
&gt;&gt; Anyway we are not there yet.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; Cheers,<br>
&gt;&gt; -- Brice<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; On Fri, Aug 3, 2012 at 4:50 PM, welk &lt;<a href=3D"mailto:kandpwe=
l...@gmail.com" target=3D"_blank">kandpwel...@gmail.com</a>&gt; wrote:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Hey James, good to see you.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Again, I have never tried to fork Mockito, or offer patches, e=
tc. =C2=A0So<br>
&gt;&gt;&gt; I don&#39;t know that pain, nor can I compare that to Github, =
but I have<br>
&gt;&gt;&gt; done Googlecode code reviews and I find them very intuitive an=
d<br>
&gt;&gt;&gt; doable. =C2=A0I also *much* prefer the documentation/wiki and =
Issues<br>
&gt;&gt;&gt; features on Googlecode (as Brice has suggested they keep those=
 things<br>
&gt;&gt;&gt; here). =C2=A0Frankly, whenever, I have to navigate thru Github=
 as a casual<br>
&gt;&gt;&gt; user, I am much more frustrated -- especially code browsig. =
=C2=A0GC AJAX<br>
&gt;&gt;&gt; tree view is much easier to use.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; But, I again I confess that my use of Mockito has been essenti=
ally<br>
&gt;&gt;&gt; confined to source/issue/release/documentation browsing, and n=
ot<br>
&gt;&gt;&gt; really anything on team development efforts. =C2=A0My own goog=
lecode<br>
&gt;&gt;&gt; development project has only had 2 users, no forks, and I have=
 done<br>
&gt;&gt;&gt; 95% of the development. =C2=A0So my pain points are more limit=
ed than<br>
&gt;&gt;&gt; perhaps those who are impacted most by the decision to move or=
 stay.<br>
&gt;&gt;&gt; I really would like to understand more for my own benefit.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; On Aug 2, 2:56 pm, James Carr &lt;<a href=3D"mailto:james.r.c.=
....@gmail.com" target=3D"_blank">james.r.c...@gmail.com</a>&gt; wrote:<br>
&gt;&gt;&gt; &gt; Well, for the most part github is more of a reason in its=
elf to use<br>
&gt;&gt;&gt; &gt; github rather than git. Bitbucket offered git support las=
t year at<br>
&gt;&gt;&gt; &gt; prices cheaper than what we pay github for but we stuck w=
ith github<br>
&gt;&gt;&gt; &gt; for a lot of the features, such as code reviews, comments=
, painless<br>
&gt;&gt;&gt; &gt; forking, etc.<br>
&gt;&gt;&gt; &gt;<br>
&gt;&gt;&gt; &gt; You can contribute to a F/OSS project on github without e=
ven knowing<br>
&gt;&gt;&gt; &gt; git. The barrier to entry is pretty low.<br>
&gt;&gt;&gt; &gt;<br>
&gt;&gt;&gt; &gt; Thanks,<br>
&gt;&gt;&gt; &gt; James<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; --<br>
&gt;&gt;&gt; You received this message because you are subscribed to the Go=
ogle Groups<br>
&gt;&gt;&gt; &quot;mockito&quot; group.<br>
&gt;&gt;&gt; To post to this group, send email to <a href=3D"mailto:mockito=
@googlegroups.com" target=3D"_blank">mockito@googlegroups.com</a>.<br>
&gt;&gt;&gt; To unsubscribe from this group, send email to<br>
&gt;&gt;&gt; <a href=3D"mailto:mockito%2Bunsubscribe@googlegroups.com" targ=
et=3D"_blank">mockito+unsubscribe@googlegroups.com</a>.<br>
&gt;&gt;&gt; For more options, visit this group at<br>
&gt;&gt;&gt; <a href=3D"http://groups.google.com/group/mockito?hl=3Den" tar=
get=3D"_blank">http://groups.google.com/group/mockito?hl=3Den</a>.<br>
&gt;&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; --<br>
&gt;&gt; You received this message because you are subscribed to the Google=
 Groups<br>
&gt;&gt; &quot;mockito&quot; group.<br>
&gt;&gt; To post to this group, send email to <a href=3D"mailto:mockito@goo=
glegroups.com" target=3D"_blank">mockito@googlegroups.com</a>.<br>
&gt;&gt; To unsubscribe from this group, send email to<br>
&gt;&gt; <a href=3D"mailto:mockito%2Bunsubscribe@googlegroups.com" target=
=3D"_blank">mockito+unsubscribe@googlegroups.com</a>.<br>
&gt;&gt; For more options, visit this group at<br>
&gt;&gt; <a href=3D"http://groups.google.com/group/mockito?hl=3Den" target=
=3D"_blank">http://groups.google.com/group/mockito?hl=3Den</a>.<br>
&gt;<br>
&gt;<br>
&gt; --<br>
&gt; You received this message because you are subscribed to the Google Gro=
ups<br>
&gt; &quot;mockito&quot; group.<br>
&gt; To post to this group, send email to <a href=3D"mailto:mockito@googleg=
roups.com" target=3D"_blank">mockito@googlegroups.com</a>.<br>
&gt; To unsubscribe from this group, send email to<br>
&gt; <a href=3D"mailto:mockito%2Bunsubscribe@googlegroups.com" target=3D"_b=
lank">mockito+unsubscribe@googlegroups.com</a>.<br>
&gt; For more options, visit this group at<br>
&gt; <a href=3D"http://groups.google.com/group/mockito?hl=3Den" target=3D"_=
blank">http://groups.google.com/group/mockito?hl=3Den</a>.<br>
<br>
--<br>
You received this message because you are subscribed to the Google Groups &=
quot;mockito&quot; group.<br>
To post to this group, send email to <a href=3D"mailto:mockito@googlegroups=
.com" target=3D"_blank">mockito@googlegroups.com</a>.<br>
To unsubscribe from this group, send email to <a href=3D"mailto:mockito%2Bu=
nsubscribe@googlegroups.com" target=3D"_blank">mockito+unsubscribe@googlegr=
oups.com</a>.<br>
For more options, visit this group at <a href=3D"http://groups.google.com/g=
roup/mockito?hl=3Den" target=3D"_blank">http://groups.google.com/group/mock=
ito?hl=3Den</a>.<br>
<br>
</div></div></blockquote></div><br></div></div></div></div><div><div>

<p></p>

-- <br>
You received this message because you are subscribed to the Google Groups &=
quot;mockito&quot; group.<br>
To post to this group, send email to <a href=3D"mailto:mockito@googlegroups=
.com" target=3D"_blank">mockito@googlegroups.com</a>.<br>
To unsubscribe from this group, send email to <a href=3D"mailto:mockito%2Bu=
nsubscribe@googlegroups.com" target=3D"_blank">mockito+unsubscribe@googlegr=
oups.com</a>.<br>

For more options, visit this group at <a href=3D"http://groups.google.com/g=
roup/mockito?hl=3Den" target=3D"_blank">http://groups.google.com/group/mock=
ito?hl=3Den</a>.<br>


</div></div></blockquote></div><br></div></div></div><div class=3D"HOEnZb">=
<div class=3D"h5">

<p></p>

-- <br>
You received this message because you are subscribed to the Google Groups &=
quot;mockito&quot; group.<br>
To post to this group, send email to <a href=3D"mailto:mockito@googlegroups=
.com" target=3D"_blank">mockito@googlegroups.com</a>.<br>
To unsubscribe from this group, send email to <a href=3D"mailto:mockito%2Bu=
nsubscribe@googlegroups.com" target=3D"_blank">mockito+unsubscribe@googlegr=
oups.com</a>.<br>

For more options, visit this group at <a href=3D"http://groups.google.com/g=
roup/mockito?hl=3Den" target=3D"_blank">http://groups.google.com/group/mock=
ito?hl=3Den</a>.<br>


</div></div></blockquote></div><br>

--0015173fe698af7bb304c6ae08d4--
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
Account Options
