+1.
Thanks Brian for all your effort and commitment.
Regards,
Ina Panova
Software Engineer| Pulp| Red Hat Inc.
"Do not go where the path may lead,
go instead where there is no path and leave a trail."
On Thu, Aug 10, 2017 at 9:58 PM, Daniel Alley wrote:
> +1
>
> On Thu, Aug 10, 20
+1
On Fri, Aug 11, 2017 at 4:54 AM, Ina Panova wrote:
> +1.
> Thanks Brian for all your effort and commitment.
>
>
>
>
> Regards,
>
> Ina Panova
> Software Engineer| Pulp| Red Hat Inc.
>
> "Do not go where the path may lead,
> go instead where there is no path and leave a trail."
>
> O
+1 to adopting this idea. @mhrivnak your summary sounds good.
What is the next step to doing this?
On Thu, Aug 10, 2017 at 11:36 AM, Michael Hrivnak
wrote:
> This seems like a good approach. I'd summarize it as:
>
> Try hard to put the documentation for each field of a model only on the
> corre
FYI, I added an option [0] called --base-dir to the checkout.py script [1]
which allows the tool to operate on a checkout in any part of the
filesystem. With this I was able to get both a Pulp2 and Pulp3 vagrant box
both running and usable at the same time!
I also cherry picked the checkout.py scr
