monotone - Bugs: bug #21115, A "revision bundle" to...
You are not allowed to post comments on this tracker with your current authentication level.
bug #21115: A "revision bundle" to send upstream when you lack push permissions
Submitter: | None | ||
Submitted: | Tue 18 Sep 2007 11:14:47 PM UTC | ||
Category: | None | Severity: | 3 - Normal |
Item Group: | feature request | Status: | None |
Privacy: | Public | Assigned to: | None |
Open/Closed: | Open | ||
mtn version --full: | monotone 0.34 (base revision: 6ae6de16b31495a773ac3002505ad51f2e4a8616)
|
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follows 1 latest change.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2007-09-18 | resiak | Carbon-Copy | - | Added resiak |
Powered by Savane 3.13-f8d8.
Corresponding source code
One of the benefits of distributed version control is that you get all the advantages of VC without needing permission to push your changes back upstream. However, suppose I write some patches for a project to whose repository I may not push. Ideally, I would commit them locally, signing them with my key, and then somehow get them added, with my signature, to the repo if the patch is accepted.
Currently, I could get diffs of the revisions and attach them to bugs on the project's bug tracking system, but then when they are committed they are not signed by me. Also, there is the risk that upstream would apply them, then make changes before they commit, creating neverending divergence at my end when i subsequently pull (unless i kill_rev_locally).
Alternatively, I could use `mtn serve` to allow a developer to pull from my repo. However, this is often not ideal: maybe I don't have permission to poke the necessary holes in a firewall, or live in a different timezone.
It would be great to have some kind of `mtn push --bundle foo.com` command which makes as if to push local revs to foo.com but in fact stashes them in a file I could attach to a bug upstream.