-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wed, 21 Oct 2009, Chris Lumens wrote:
We have a rhel6-branch, so vacuum up things from RHEL-6 dist-cvs and put
them in git.
Wasn't the plan to make sure anything committed to the RHEL-6 branch also
went to the master branch and in time retire the RHEL-6 branch and make a
new RHEL-6 branch out of the master one ?
I'll probably just do it as a merge, so we'll pull in all the commits
from master but also retain these couple RHEL-specific things. So, it
should be safe to commit them to rhel6-branch and not have them get
lost.
Right, if we put those changes in to git now, we can track them and not have
to maintain a set of patches in dist-cvs. A merge of master on to
rhel6-branch should work for us in this case so we don't lose the rhel6
specifics.
In light of that, we really want to check every one of these patches and
determine whether it's RHEL-specific, or applies to both.
I'm pretty sure all of these are RHEL-specific.
- --
David Cantrell <dcantrell@xxxxxxxxxx>
Red Hat / Honolulu, HI
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkrfdMgACgkQ5hsjjIy1VkkQ9wCg5yWR8p/lZxaE3wkmAPESqEY5
cFEAn1RbTIS3a7DJ1sw5/wNp3QxcYFwu
=YNfM
-----END PGP SIGNATURE-----
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
