Thanks David & Russell for the inisght and clarifications.
Cheers,
-Lyndon-
Lyndon Washington
w: http://blog.the-washingtons.com/
On Sat, Nov 8, 2008 at 11:59 AM, Russell Bryant <[EMAIL PROTECTED]>wrote:
>
>
> On Sat, Nov 8, 2008 at 10:35 AM, Lyndon Washington <
> [EMAIL PROTECTED]> wrote:
>
>
On Sat, Nov 8, 2008 at 10:35 AM, Lyndon Washington <
[EMAIL PROTECTED]> wrote:
> We are planning to move to Subversion for some of our projects. Is the
> experience any different with that repository?
I do this with subversion. Basically, developers do their work in branches
off of trunk, for
We are planning to move to Subversion for some of our projects. Is the
experience any different with that repository?
Cheers,
-Lyndon-
Lyndon Washington
w: http://blog.the-washingtons.com/
On Fri, Nov 7, 2008 at 5:46 PM, David Trowbridge <[EMAIL PROTECTED]> wrote:
>
> With Perforce, review req
With Perforce, review requests are tied to changeset numbers. What you
describe would involve creating a new review request. This is because
we wrote it with pre-commit reviews in mind instead of post-commit.
-David
On Fri, Nov 7, 2008 at 2:37 PM, Lyndon Washington
<[EMAIL PROTECTED]> wrote:
> H
Hi,
I think I read this somewhere, or maybe I just dreamed it . . .
Scenario is . . .
1. implement some changes and commit to perforce repo.
2. submit and publish a review request for that changeset.
3. get feedback
4. incorporate feedback and commit once again.
5. update the ori
