So I have to wait until de right files are commited in the Git?

> Date: Mon, 15 Feb 2016 09:12:20 -0500
> Subject: Re: oc v1.1.2-dirty
> From: [email protected]
> To: [email protected]
> CC: [email protected]; [email protected]
> 
> This is actually in the copr RPM build I had done. At the time that I
> built the SRPM I had a new uncommitted file in my git checkout. I've
> verified that the contents of the RPM are unaffected. We'll address
> this release process deficiency as we get automated builds ready for
> Centos.
> 
> On Mon, Feb 15, 2016 at 8:45 AM, Brenton Leanhardt <[email protected]> 
> wrote:
> > On Mon, Feb 15, 2016 at 8:07 AM, Den Cowboy <[email protected]> wrote:
> >> Why is this the name of this version?
> >> oc v1.1.2-dirty
> >>
> >> Is it because of the new layout or is it deprecated/broken?
> >
> > I think you'll see this when you perform a build with files in your
> > repository that aren't committed.
> >
> >
> >>
> >> _______________________________________________
> >> users mailing list
> >> [email protected]
> >> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
> >>
> >
> > _______________________________________________
> > users mailing list
> > [email protected]
> > http://lists.openshift.redhat.com/openshiftmm/listinfo/users
                                          
_______________________________________________
users mailing list
[email protected]
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Reply via email to