On Wed, 2009-12-23 at 14:23 -0800, Roland McGrath wrote: > > I understand the use case, I'm still not super keen on having official > > built packages come out of a branch. Makes discovery somewhat > > difficult, and leads to problems if we have to bump+build something and > > don't realize that the real live code is actually on a branch. > > Surely all previous builds will be easy to "discover" in koji and that will > tell you the exact commit id. AIUI there should be an automagic git tag > pushed by koji so that just directly in git alone it is trivial and > reliable to find the commit matching a given build. In git the idea of a > branch is not inherently a permanent thing, and only the ancestry graph of > a particular commit is truly meaningful as historical information. Just > the commit id of interest is what you need to ascertain whether it is the > head or ancestor of which branches at the time you ask the question. > > Right, but when I as a releng person need to bump something in an emergency or when a maintainer is out, I expect origin/master to be "live" for rawhide, ditto origin/F-12 for Fedora 12. I don't expect that I'd have to go hunting down where the commit hash for the previous build came from, then try to discover which branch that commit hash currently lives on, so that I can commit on top of it and keep going. -- Jesse Keating Fedora -- Freedom² is a feature! identi.ca: http://identi.ca/jkeating
Attachment:
signature.asc
Description: This is a digitally signed message part
-- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
