-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 9/1/10 9:01 AM, Garrett Holmstrom wrote: > Andreas Schwab wrote: >> Matt McCutchen <matt@xxxxxxxxxxxxxxxxx> writes: >>> I propose that fedpkg should consider a --dist option, a "branch" >>> file, and the name of the current git branch in that order. >> >> Or make it a branch config (eg. git config branch.$branch.dist f14). > > This, please. Using magical branch names or files to decide what > release a branch corresponds to seems silly when it can be a property of > the branch itself. We essentially do this now. We look at the branch merge point, which tells me what upstream Fedora/RHEL branch you're tracking, which tells me how to set the macros. It's only when you aren't tracking a remote branch that things go south. - -- Jesse Keating Fedora -- Freedom² is a feature! identi.ca: http://identi.ca/jkeating -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkx+h/0ACgkQ4v2HLvE71NX6AwCfRi4C1WSGlPbL2sFQL63fbY6a +rcAn2/rV3UCd16FTp7DiwSpiQRsXi33 =lB12 -----END PGP SIGNATURE----- -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
