drop inheritance at f19 branch point?

[Richard W.M. Jones]

On Thu, Jan 24, 2013 at 06:07:08PM +0100, Lennart Poettering wrote:
> On Thu, 24.01.13 10:22, Richard W.M. Jones (rjones at redhat.com) wrote:
> 
> > On Thu, Jan 24, 2013 at 10:38:00AM +0100, Vít Ondruch wrote:
> > > And I disagree with this proposal.
> > > 
> > > It is mixed for me. Sometimes, I'd like to update in Rawhide,
> > > especially if the freeze is taking long, while in other cases, I
> > > need to do some bugfix in my packages which is found during testing
> > > and needs to be applied to both branches. In this case, the
> > > inheritance saves my work, while disabling the inheritance would
> > > always duplicate my work. So the current state is ideal from my POV.
> > 
> > It doesn't duplicate your work, although it increases it a little.
> > 
> > If you keep the history of master and the fX branches consistent, and
> > use 'fedpkg clone -B', then what you actually have to do is:
> > 
> >  - make the change in package/master
> >  - fedpkg push && fedpkg build --nowait
> >  - cd ../f18
> >  - git pull ../master
> >  - fedpkg push && fedpkg build --nowait
> 
> The "--nowait" doesn't really work. I do care if the build I did
> finished successfully. With the lines above you kinda suggest that
> people shouldn't care about build results... Just updating my spec file
> and issuing a build request in "fire and forget" doesn't work.

It sends you an email when it's done.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
virt-df lists disk usage of guests without needing to install any
software inside the virtual machine.  Supports Linux and Windows.
http://people.redhat.com/~rjones/virt-df/