{"thread":{"id":"6160","subject":"Strict ordering by date","startedAt":"2006-12-31T01:03:31Z","lastAt":"2006-12-31T01:03:31Z","messageCount":1,"participants":["H. Peter Anvin"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"30524","messageId":"45970C63.1020509@zytor.com","threadId":"6160","inReplyTo":null,"subject":"Strict ordering by date","fromName":"H. Peter Anvin","fromEmail":"hpa@zytor.com","sentAt":"2006-12-31T01:03:31Z","receivedAt":"2006-12-31T01:03:31Z","isPatch":false,"sender":{"key":"hpa@zytor.com","avatar":null},"body":"Hi all,\n\nI have added a --pretty=rpm option to git in order to automatically \ngenerate the changelog for an RPM specfile.  So far, so good. \nUnfortunately, rpmbuild is very picky and will simply refuse to run, at \nall, if any of the entries are out of reverse chronological order.  When \ndealing with merges or cherrypicking -- or, for that matter, a commit \ndone with a broken time setting -- this doesn't work with either \n--date-order or --topo-order.\n\n(And yes, this is an rpmbuild misfeature.)\n\nI've tried to add a --strict-date-order option, but it's not clear at \nwhat point -- if any -- we actually have the full list of entries to \ndisplay.  It doesn't seem to happen anywhere inside revision.c.\n\nAny pointers appreciated.\n\n\t-hpa\n"}]}