Stephan Kulow 2784171f75 Create fake revisions for every commit in the base of a linked package ... This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part		2022-10-26 14:56:38 +02:00
..
binary.py	Move modules into lib subdir	2022-10-17 19:56:41 +02:00
config.py	Move modules into lib subdir	2022-10-17 19:56:41 +02:00
db_revision.py	Create fake revisions for every commit in the base of a linked package	2022-10-26 14:56:38 +02:00
db.py	Create fake revisions for every commit in the base of a linked package	2022-10-26 14:56:38 +02:00
exporter.py	Create fake revisions for every commit in the base of a linked package	2022-10-26 14:56:38 +02:00
git.py	Move modules into lib subdir	2022-10-17 19:56:41 +02:00
history.py	Split Revision into OBS and DB	2022-10-18 12:17:43 +02:00
importer.py	Create fake revisions for every commit in the base of a linked package	2022-10-26 14:56:38 +02:00
obs_revision.py	Create fake revisions for every commit in the base of a linked package	2022-10-26 14:56:38 +02:00
obs.py	fixed formatting and other suggestions	2022-10-26 11:58:01 +02:00
proxy_sha256.py	Move modules into lib subdir	2022-10-17 19:56:41 +02:00
request.py	Implement a fileshash function for revision	2022-10-26 14:15:42 +02:00
tree_builder.py	Create fake revisions for every commit in the base of a linked package	2022-10-26 14:56:38 +02:00
user.py	fixed formatting and other suggestions	2022-10-26 11:58:01 +02:00