tools/git-repo.git, branch v1.4.2Mirror of gerrit.googlesource.com/git-repohttps://git.enea.com/cgit/tools/git-repo.git/atom?h=v1.4.22008-12-12T16:04:07+00:00Describe upload --replace in upload's help text2008-12-12T16:04:07+00:00Shawn O. Pearcesop@google.com2008-12-12T16:04:07+00:00urn:sha1:a6df7d284cc008cc2f21092f5fdd4e32ed28500e
Signed-off-by: Shawn O. Pearce <sop@google.com>
Don't accept multiple commits for the same change in upload --replace2008-12-12T16:01:12+00:00Shawn O. Pearcesop@google.com2008-12-12T16:01:12+00:00urn:sha1:67092448c290ce6bd3f05abc17f4f4d53e4c91bb
Gerrit won't permit more than one commit using the same change
number during a replacement request, so we should error out if
the user has asked for this in their upload edit script.
Signed-off-by: Shawn O. Pearce <sop@google.com>
Fix upload --replace after it was broken when --review,--cc was added2008-11-24T23:51:25+00:00Shawn O. Pearcesop@google.com2008-11-24T23:51:25+00:00urn:sha1:e92ceebde0034ad045e12b8241045d701383e681
Signed-off-by: Shawn O. Pearce <sop@google.com>
Support <remove-project name="X"> in manifest to remove/replace X2008-11-20T19:54:46+00:00Shawn O. Pearcesop@google.com2008-11-20T19:42:22+00:00urn:sha1:03eaf07ec6aa7e99a0444ac1ec708b2a5f7cbbf5
The manifest files now permit removing a project so the user can
either keep it out of their client, or replace it with a different
project using an entirely different configuration.
Signed-off-by: Shawn O. Pearce <sop@google.com>
Add --review and --cc flags to repo upload, so you can2008-11-19T16:55:06+00:00Joe Onoratojoeo@android.com2008-11-17T21:56:36+00:00urn:sha1:2896a79120fe1de65472736f756c47b558b44db1
assign reviewers when you upload changes.
Make repo's editor work when the editor is a commandline with2008-11-15T02:12:44+00:00Joe Onoratojoeo@android.com2008-11-15T02:12:44+00:00urn:sha1:8c6eef4713db36a2063dd5a68b3d37a5e4276508
multiple args.
Paper bag fix repo 1.3's "repo upload" without --replace2008-11-13T02:37:18+00:00Shawn O. Pearcesop@google.com2008-11-13T02:37:18+00:00urn:sha1:34d237fbfbd87e8bb81063c23737e9b1ee4d5679
If we aren't doing a replacement we do not have any
replace rules, so we cannot iterate over them.
Signed-off-by: Shawn O. Pearce <sop@google.com>
Teach 'repo upload --replace' how to add replacement patch sets2008-11-12T17:12:19+00:00Shawn O. Pearcesop@google.com2008-11-12T01:12:43+00:00urn:sha1:c99883fee990a1baa7e0bf5f854c7485b7d0f0d9
Users are prompted with the list of known changes we are about
to upload, and they can fill out the current change numbers for
any changes which already exist in the data store. For each of
those changes the change number and commit id is sent as part of
the upload request, so Gerrit can insert the new commit as a new
patch set of the existing change, rather than make a new change.
This facility permits developers to replace a patch so they can
address comments made on a prior version of the same change.
Signed-off-by: Shawn O. Pearce <sop@google.com>
Update proto client to support patch set replacments2008-11-12T17:12:19+00:00Shawn O. Pearcesop@google.com2008-11-12T02:45:55+00:00urn:sha1:ec18b4bac4f3c0760c26e83b8ade01ad1c815a9b
Signed-off-by: Shawn O. Pearce <sop@google.com>
Refactor part of GetUploadableBranches to lookup one specific branch2008-11-12T17:12:17+00:00Shawn O. Pearcesop@google.com2008-11-12T01:03:13+00:00urn:sha1:35f2596c27ae041235b88076888870b8ba2e2c8c
This way project.GetUploadableBranch(project.CurrentBranch) can tell
us how (if at all) to upload the currently checked out branch.
Signed-off-by: Shawn O. Pearce <sop@google.com>