On Tue, Jun 23, 2015 at 1:11 PM, Pali Rohár wrote:
>
> It is basically to deliver what have you done and something which you
> can show to other people...
>
> With that I means to prepare code in your git branch to some state which
> can be compiled and maybe also easily reused/merged (if possibl
On Tuesday 23 June 2015 09:31:16 R.Harish Navnit wrote:
> Hey Pali,
>
> On Mon, Jun 22, 2015 at 12:56 PM, Pali Rohár wrote:
>
> > By June 26 please prepare or update your git
> > repositories so your code can be "evaluated". Try to prepare code to
> > state which could be "presented" by you to a
Hey Pali,
On Mon, Jun 22, 2015 at 12:56 PM, Pali Rohár wrote:
> By June 26 please prepare or update your git
> repositories so your code can be "evaluated". Try to prepare code to
> state which could be "presented" by you to audience (some demo)...
>
I'm just curious to know who would the audien
Sure :)
On Jun 22, 2015 12:56 PM, "Pali Rohár" wrote:
> Hello,
>
> I just want to remind you that at June 26 starts mid term evaluation. By
> that day I would like to see from you updated progress timeline what
> have you finished and what not according to plan. This will be useful
> also for you
Sure thing Pali! I'm on it. :)
2015-06-22 10:26 GMT+03:00 Pali Rohár :
> Hello,
>
> I just want to remind you that at June 26 starts mid term evaluation. By
> that day I would like to see from you updated progress timeline what
> have you finished and what not according to plan. This will be usef
Hello,
I just want to remind you that at June 26 starts mid term evaluation. By
that day I would like to see from you updated progress timeline what
have you finished and what not according to plan. This will be useful
also for you to see how you can work and deliver updates from your
planned time
