On Fri, Dec 05, 2014 at 10:37:39AM +0800, Paul Wise wrote:
> On Thu, Dec 4, 2014 at 11:16 PM, Corentin Desfarges wrote:
>
> > The file is just used by one of the unit tests. But there are more than 20
> > unit tests which need their own specific data to work.
>
> Personally I'm now leaning toward
On Thu, Dec 4, 2014 at 11:16 PM, Corentin Desfarges wrote:
> The file is just used by one of the unit tests. But there are more than 20
> unit tests which need their own specific data to work.
Ok, that makes this a bit more complicated, especially since the
amount of data could grow over time.
P
I guess that this new orig.tar.gz would be created by using uscan (if the
link is added in d/watch) ?
Uscan requires the file to be on a webserver somewhere. I think you
would just create it manually using this:
tar Jcf fw4spl_0.1.orig-testdata.tar.xz md_1.jsonz
Then add a debian/README.sou
Hi
> Can you link to the file we are talking about?
With the authorization of the responsibles of the project, I published the file
here [2]
[2]http://goo.gl/53sAzM
this looks a bit weird. I guess this google thing allows you to inspect the
content of zip files?
Yes indeed. I simply upload
On Thu, Dec 4, 2014 at 10:17 PM, Corentin Desfarges wrote:
> It's not about a real patient...
> So I don't think that there is any problem of confidentiality in this case.
Fair enough.
> I guess that this new orig.tar.gz would be created by using uscan (if the
> link is added in d/watch) ?
Usca
Hi
With the authorization of the responsibles of the project, I published the
file here [2]
It contains the names of one patient and his birth date so that
probably wasn't a good idea. This file appears to contain CT scan
results in a custom format? I can't view the scan itself as the
softwar
6 matches
Mail list logo
