Re: Best Approach to Reconstruct Repo with Changes

2015-04-28 Thread David Trowbridge
Hi,

Internally, in the case of an unpushed branch, Review Board does store a
parent diff between the parent revision and the posted diff. However,
this is not exposed to the user. Typically what will happen in this case is
that the parent changes will have their own review requests, in which case
they can be applied in order (the Depends On field is useful to indicate
to others the relationship). Sometimes I'll ask someone to update the
review request with a change that applies cleanly to a specific branch.

We're working on dramatically improving our DVCS capabilities, specifically
with regards to posting entire branches at once. This will make it so every
commit on the branch will be included, and `rbt patch` will be able to
apply the entire branch at once, reproducing the commits exactly.

-David

On Thu, Apr 23, 2015 at 4:09 PM jameslam91...@gmail.com wrote:

 Hello Review Board users / developers,

 What is the recommended approach for reconstructing a work copy of the
 changes in a review request?

 I am most specifically interested in Git where branching may occur.

 It seems that an approach would be to

 1. Checkout the repo with the base revision which I can get from the
 Review Board API.
 2. rbt patch to apply the changes

 However, it seems that I can't always just checkout from the base revision
 as that revision may be in a unpushed branch.

 How can I reconstruct the repo up to the point where the base revision is
 if I can't directly check out the changes. Does Review Board store all the
 diffs leading up to the uploaded diff for branches? Is this information
 exposed to the user?

 Thanks!

 --
 Supercharge your Review Board with Power Pack:
 https://www.reviewboard.org/powerpack/
 Want us to host Review Board for you? Check out RBCommons:
 https://rbcommons.com/
 Happy user? Let us know! https://www.reviewboard.org/users/
 ---
 You received this message because you are subscribed to the Google Groups
 reviewboard group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to reviewboard+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.


-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
reviewboard group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Best Approach to Reconstruct Repo with Changes

2015-04-23 Thread jameslam91744
Hello Review Board users / developers,

What is the recommended approach for reconstructing a work copy of the 
changes in a review request?

I am most specifically interested in Git where branching may occur.

It seems that an approach would be to 

1. Checkout the repo with the base revision which I can get from the Review 
Board API.
2. rbt patch to apply the changes

However, it seems that I can't always just checkout from the base revision 
as that revision may be in a unpushed branch.

How can I reconstruct the repo up to the point where the base revision is 
if I can't directly check out the changes. Does Review Board store all the 
diffs leading up to the uploaded diff for branches? Is this information 
exposed to the user?

Thanks!

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
reviewboard group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.