bugmonotone - Bugs: bug #21115, A "revision bundle" to...

 
 

You are not allowed to post comments on this tracker with your current authentification level.

bug #21115: A "revision bundle" to send upstream when you lack push permissions

Submitted by:  None
Submitted on:  Tue 18 Sep 2007 11:14:47 PM UTC  
 
Category: NoneSeverity: 3 - Normal
Item Group: feature requestStatus: None
Privacy: PublicAssigned to: None
Open/Closed: Open
mtn version --full: 

monotone 0.34 (base revision: 6ae6de16b31495a773ac3002505ad51f2e4a8616)
Running on : Linux 2.6.20-16-generic #2 SMP Fri Aug 31 00:55:27 UTC 2007 i686
C++ compiler : GNU C++ version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)
C++ standard library: GNU libstdc++ version 20061115
Boost version : 1_33_1
Changes since base revision:
format_version "1"

new_manifest [0c2f96e14d290841a5111d69ad03174c391776a4]

old_revision [6ae6de16b31495a773ac3002505ad51f2e4a8616]

Generated from data cached in the distribution;
further changes may have been made.

Tue 18 Sep 2007 11:14:47 PM UTC, original submission:

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.

Anonymous

 

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -unavailable- added by resiak
  •  

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    Follows 1 latest change.

    Date Changed By Updated Field Previous Value => Replaced By
    Tue 18 Sep 2007 11:30:11 PM UTCresiakCarbon-Copy-=>Added resiak

    Back to the top


    Powered by Savane 3.1-cleanup