)]}' { "log": [ { "commit": "6392c879454bd4fa0e770195ee8424e383d17df2", "tree": "bfbfedb0a1d7f3fbe648deaf09e570ba347feeb0", "parents": [ "97d2b2f7a087bfc695536ae9be962406d82152f2" ], "author": { "name": "Shawn O. Pearce", "email": "sop@google.com", "time": "Thu Sep 22 17:44:31 2011 -0700" }, "committer": { "name": "Shawn O. Pearce", "email": "sop@google.com", "time": "Thu Sep 22 18:08:27 2011 -0700" }, "message": "sync: Allow -j to have a default in manifest\n\nThis permits manifest authors to suggest a number of parallel\nfetch operations against a remote server. For example, Gerrit\nCode Review servers support queuing of requests and processes\nthem in first-in, first-out order. Running concurrent fetches\ncan utilize multiple CPUs on the Gerrit server, but will also\ndecrease overall operation latency by having the request put\ninto the queue ready to execute as soon as a CPU is free.\n\nChange-Id: I3d3904acb6f63516bae4b071c510ad57a2afab18\nSigned-off-by: Shawn O. Pearce \u003csop@google.com\u003e\n" }, { "commit": "37282b4b9c5b1d9a1ff07f7f0686a81b65a0a5c6", "tree": "aba568b85d38de4cfef90cd771169c9422aef09c", "parents": [ "835cd6888f16ff30a3428adfa3a775efad918880" ], "author": { "name": "Doug Anderson", "email": "dianders@google.com", "time": "Fri Mar 04 11:54:18 2011 -0800" }, "committer": { "name": "Shawn O. Pearce", "email": "sop@google.com", "time": "Fri Mar 11 11:53:23 2011 -0800" }, "message": "Support repo-level pre-upload hook and prep for future hooks.\n\nAll repo-level hooks are expected to live in a single project at the\ntop level of that project. The name of the hooks project is provided\nin the manifest.xml. The manifest also lists which hooks are enabled\nto make it obvious if a file somehow failed to sync down (or got\ndeleted).\n\nBefore running any hook, we will prompt the user to make sure that it\nis OK. A user can deny running the hook, allow once, or allow\n\"forever\" (until hooks change). This tries to keep with the git\nspirit of not automatically running anything on the user\u0027s computer\nthat got synced down. Note that individual repo commands can add\nalways options to avoid these prompts as they see fit (see below for\nthe \u0027upload\u0027 options).\n\nWhen hooks are run, they are loaded into the current interpreter (the\none running repo) and their main() function is run. This mechanism is\nused (instead of using subprocess) to make it easier to expand to a\nricher hook interface in the future. During loading, the\ninterpreter\u0027s sys.path is updated to contain the directory containing\nthe hooks so that hooks can be split into multiple files.\n\nThe upload command has two options that control hook behavior:\n - no-verify\u003dFalse, verify\u003dFalse (DEFAULT):\n If stdout is a tty, can prompt about running upload hooks if needed.\n If user denies running hooks, the upload is cancelled. If stdout is\n not a tty and we would need to prompt about upload hooks, upload is\n cancelled.\n - no-verify\u003dFalse, verify\u003dTrue:\n Always run upload hooks with no prompt.\n - no-verify\u003dTrue, verify\u003dFalse:\n Never run upload hooks, but upload anyway (AKA bypass hooks).\n - no-verify\u003dTrue, verify\u003dTrue:\n Invalid\n\nSample bit of manifest.xml code for enabling hooks (assumes you have a\nproject named \u0027hooks\u0027 where hooks are stored):\n \u003crepo-hooks in-project\u003d\"hooks\" enabled-list\u003d\"pre-upload\" /\u003e\n\nSample main() function in pre-upload.py in hooks directory:\n def main(project_list, **kwargs):\n print (\u0027These projects will be uploaded: %s\u0027 %\n \u0027, \u0027.join(project_list))\n print (\u0027I am being a good boy and ignoring anything in kwargs\\n\u0027\n \u0027that I don\\\u0027t understand.\u0027)\n print \u0027I fail 50% of the time. How flaky.\u0027\n if random.random() \u003c\u003d .5:\n raise Exception(\u0027Pre-upload hook failed. Have a nice day.\u0027)\n\nChange-Id: I5cefa2cd5865c72589263cf8e2f152a43c122f70\n" }, { "commit": "2b8db3ce3e7344b9f3b5216637c5af0d54be5656", "tree": "10f0c759efdade6a556eac16b46160b4843135d5", "parents": [ "5df6de075e5fb674368d38f858419425bc8d8d07" ], "author": { "name": "Doug Anderson", "email": "dianders@google.com", "time": "Mon Nov 01 15:08:06 2010 -0700" }, "committer": { "name": "Doug Anderson", "email": "dianders@google.com", "time": "Mon Nov 01 15:08:06 2010 -0700" }, "message": "Added feature to print a \u003cnotice\u003e from manifest at the end of a sync.\n\nThis feature is used to convey information on a when a branch has\nceased development or if it is an experimental branch with a few\ngotchas, etc.\n\nYou add it to your manifest XML by doing something like this:\n\u003cmanifest\u003e\n \u003cnotice\u003e\n NOTE TO DEVELOPERS:\n If you checkin code, you have to pinky-swear that it contains no bugs.\n Anyone who breaks their promise will have tomatoes thrown at them in the\n team meeting. Be sure to bring an extra set of clothes.\n \u003c/notice\u003e\n\n \u003cremote ... /\u003e\n ...\n\u003c/manifest\u003e\n\nCarriage returns and indentation are relevant for the text in this tag.\n\nThis feature was requested by Anush Elangovan on the ChromiumOS team.\n" }, { "commit": "a1bfd2cd7253b1662e08f5ec5be3d863430c756c", "tree": "48cf4d0a983e37b50220cecc043793d6a5f0c319", "parents": [ "6d7508b3d52781a3f8170a4257c65e2de176cc68" ], "author": { "name": "Nico Sallembien", "email": "nsallembien@google.com", "time": "Tue Apr 06 10:40:01 2010 -0700" }, "committer": { "name": "Nico Sallembien", "email": "nsallembien@google.com", "time": "Tue Apr 13 10:20:37 2010 -0700" }, "message": "Add a \u0027smart sync\u0027 option to repo sync\n\nThis option allows the user to specify a manifest server to use when\nsyncing. This manifest server will provide a manifest pegging each\nproject to a known green build. This allows developers to work on a\nknown good tree that is known to build and pass tests, preventing\nfailed builds to hamper productivity.\n\nThe manifest used is not \"sticky\" so as to allow subsequent\n\u0027repo sync\u0027 calls to sync to the tip of the tree.\n\nChange-Id: Id0a24ece20f5a88034ad364b416a1dd2e394226d\n" }, { "commit": "242b52690d327a77e47140509085f406155c5722", "tree": "92b58b51e6f0b38bea6cc98a0c67604c5d08b7f1", "parents": [ "4cc70ce501321733a1b389e685e964d34b3b4cf5" ], "author": { "name": "Shawn O. Pearce", "email": "sop@google.com", "time": "Tue May 19 13:00:29 2009 -0700" }, "committer": { "name": "Shawn O. Pearce", "email": "sop@google.com", "time": "Tue May 19 13:01:52 2009 -0700" }, "message": "Remove support for the extra \u003cremote\u003e definitions in manifests\n\nThese aren\u0027t that widely used, and actually make it difficult for\nusers to fully mirror a forest of repositories, and then permit\nsomeone else to clone off that forest, rather then the original\nupstream servers.\n\nSigned-off-by: Shawn O. Pearce \u003csop@google.com\u003e\n" }, { "commit": "a490f03dc23792a86bbe5b2b8c89b32f39774c80", "tree": "60f1c904b47259643b40f0d7267a2136b3519c7a", "parents": [ "deec0536d657be178e8eed2d597afb9fdc716e99" ], "author": { "name": "Shawn O. Pearce", "email": "sop@google.com", "time": "Sat Apr 18 11:25:58 2009 -0700" }, "committer": { "name": "Shawn O. Pearce", "email": "sop@google.com", "time": "Sat Apr 18 11:25:58 2009 -0700" }, "message": "Correct note about local_manifest.xml capabilities\n\nWith the \u003cremove-project\u003e element we can remove projects, and\nfully replace them with a different definition. So this note\nis out of date.\n\nSigned-off-by: Shawn O. Pearce \u003csop@google.com\u003e\n" }, { "commit": "43c3d9ea17f1436a6b3b2e7e7827da6f48a21da9", "tree": "9bfa77f57095fcd04901ee7783c78d49afdb1e9d", "parents": [ "4259b8a2ac0dddb54e98e00afc454bf966d4f058" ], "author": { "name": "Shawn O. Pearce", "email": "sop@google.com", "time": "Wed Mar 04 14:26:50 2009 -0800" }, "committer": { "name": "Shawn O. Pearce", "email": "sop@google.com", "time": "Wed Mar 04 14:26:50 2009 -0800" }, "message": "Add a \u0027repo manifest\u0027 command whose help is the manifest file format\n\nThis should make it easier for users to discover the file format\non their own, and read about it.\n\nSigned-off-by: Shawn O. Pearce \u003csop@google.com\u003e\n" }, { "commit": "03eaf07ec6aa7e99a0444ac1ec708b2a5f7cbbf5", "tree": "3de33686218f59849912004a4376402082384fff", "parents": [ "2896a79120fe1de65472736f756c47b558b44db1" ], "author": { "name": "Shawn O. Pearce", "email": "sop@google.com", "time": "Thu Nov 20 11:42:22 2008 -0800" }, "committer": { "name": "Shawn O. Pearce", "email": "sop@google.com", "time": "Thu Nov 20 11:54:46 2008 -0800" }, "message": "Support \u003cremove-project name\u003d\"X\"\u003e in manifest to remove/replace X\n\nThe manifest files now permit removing a project so the user can\neither keep it out of their client, or replace it with a different\nproject using an entirely different configuration.\n\nSigned-off-by: Shawn O. Pearce \u003csop@google.com\u003e\n" }, { "commit": "70939e2f73bf118c89cf4af4988dba807c50a0ce", "tree": "b1849b9a48572876b35cd621192cbb4c712e816e", "parents": [ "ae6e0949d187c35d79dbc0b21788fdbb2c65bf78" ], "author": { "name": "Shawn O. Pearce", "email": "sop@google.com", "time": "Thu Nov 06 11:07:14 2008 -0800" }, "committer": { "name": "Shawn O. Pearce", "email": "sop@google.com", "time": "Thu Nov 06 11:23:08 2008 -0800" }, "message": "Add \u003cadd-remote to-project\u003d\"...\"\u003e to inject additional remotes\n\nThis way users can add forks they know about to an existing project\nthat was already declared in the primary manifest. This is mostly\nuseful with the Linux kernel project, where multiple forks is quite\ncommon for the main upstream tree (e.g. Linus\u0027 tree), a platform\narchitecture tree (e.g. ARM) and a device specific tree (e.g. the\nmsm7k tree used by Android).\n\nSigned-off-by: Shawn O. Pearce \u003csop@google.com\u003e\n" }, { "commit": "ae6e0949d187c35d79dbc0b21788fdbb2c65bf78", "tree": "7a825c0e8cb24f0df512f62f4e44970026641dda", "parents": [ "339ba9f6f70b1733f89a5ff89d5f155389a04094" ], "author": { "name": "Shawn O. Pearce", "email": "sop@google.com", "time": "Thu Nov 06 10:25:35 2008 -0800" }, "committer": { "name": "Shawn O. Pearce", "email": "sop@google.com", "time": "Thu Nov 06 11:23:06 2008 -0800" }, "message": "Add \u003cremote project-name\u003d\"...\"\u003e attribute within projects\n\nBy setting a project-name on a remote nested within a project forks\nof a project like the Linux kernel can be easily handled by fetching\nall relevant forks into the same client side project under different\nremote names. Developers can create branches off different remotes\nusing `git checkout --track -b $myname $remote/$branch` and later\n`repo upload` automatically redirects to the proper fork project\nin the code review server.\n\nSigned-off-by: Shawn O. Pearce \u003csop@google.com\u003e\n" }, { "commit": "70cd4ab2708eaae7d96d7e8b0a3f88850c163543", "tree": "fe973a5bbed05d4fb81019a3c43f7660ff89bc2b", "parents": [ "e284ad1d1a2c6fa0e0ac800e87b2607f9bda339e" ], "author": { "name": "Shawn O. Pearce", "email": "sop@google.com", "time": "Thu Nov 06 08:48:44 2008 -0800" }, "committer": { "name": "Shawn O. Pearce", "email": "sop@google.com", "time": "Thu Nov 06 08:48:44 2008 -0800" }, "message": "Add some short documentation about the local manifest\n\nSigned-off-by: Shawn O. Pearce \u003csop@google.com\u003e\n" }, { "commit": "3e5481999d5f853e19ee5caaaaa968fc4b5176ab", "tree": "fd6c97f1abd78525dc26b4eb2b8bc12027b7f93b", "parents": [ "d3c388391e11aff0b26ecf19c8cb668a9629ef5a" ], "author": { "name": "Shawn O. Pearce", "email": "sop@google.com", "time": "Tue Nov 04 11:19:36 2008 -0800" }, "committer": { "name": "Shawn O. Pearce", "email": "sop@google.com", "time": "Tue Nov 04 11:19:36 2008 -0800" }, "message": "Add a basic outline of the repo manifest file format\n\nSigned-off-by: Shawn O. Pearce \u003csop@google.com\u003e\n" } ] }