This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "The official pacman repository". The branch, master has been updated discards c419277dd2633b19a2a989f5b2a11cd9b4f4375b (commit) via 83fa6aa2896c0c940e8bf5b7499abc7ef955e658 (commit) This update added new revisions after undoing existing revisions. That is to say, the old revision is not a strict subset of the new revision. This situation occurs when you --force push a change and generate a repository containing something like this: * -- * -- B -- O -- O -- O (c419277dd2633b19a2a989f5b2a11cd9b4f4375b) \ N -- N -- N (83fa6aa2896c0c940e8bf5b7499abc7ef955e658) When this happens we assume that you've already had alert emails for all of the O revisions, and so we here report only the revisions in the N branch from the common base, B. Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit 83fa6aa2896c0c940e8bf5b7499abc7ef955e658 Author: Chantry Xavier Date: Sat Aug 25 00:10:40 2007 +0200 Remove duplicated get_upgrades function, use sysupgrade instead. The alpm_get_upgrades was exactly the same as find_replacements + _alpm_sync_sysupgrade, except that it automatically made the eventual replacements, without asking the user : Replace %s with %s/%s? [Y/n] The replace question, asked in find_replacements. can now be skipped by using a NULL trans argument, so that we get the same behavior as with alpm_get_upgrades. So alpm_db_get_upgrades() can now be replaced by alpm_sync_sysupgrade(db_local, syncdbs). Signed-off-by: Chantry Xavier Signed-off-by: Dan McGee ----------------------------------------------------------------------- Summary of changes: hooks/post-receive -- The official pacman repository