Gregory Szorc wrote:
Support for specifying the base revision to review has landed. Just
pull and update version-control-tools and you can use `hg push -r
base -r tip` or `hg push -r base::tip`.
\o/ Thank you!
- Blair
___
dev-platform mailing list
Hi, I've been trying MozReview and I'm having trouble with updating a
review with changes for my reviewers to verify. The documentation says,
Oh, it just works, but in my case it doesn't.
I'm using the evolve extension, so my repo have obsolescence markers,
but I don't see them being sync'd
On 11/12/14 10:39 PM, Dan Glastonbury wrote:
Hi, I've been trying MozReview and I'm having trouble with updating a
review with changes for my reviewers to verify. The documentation says,
Oh, it just works, but in my case it doesn't.
I'm using the evolve extension, so my repo have obsolescence
On 11/10/14 9:14 AM, Gregory Szorc wrote:
On 11/9/14 8:29 PM, Boris Zbarsky wrote:
On 11/9/14, 11:10 PM, Gregory Szorc wrote:
We currently only attempt to map each review/commit series to a single
bug.
This is definitely a problem; it serializes workflow such that you have
to get review on
but unimaginatively) MozReview, is
ready for general use.
In the interests of beta-testing our documentation at the same time as
our code, I want to mostly confine my post to a link to our docs:
http://mozilla-version-control-tools.readthedocs.org/en/latest/mozreview.html
Everything you need should
Board. I'm excited to announce that
this tool, now named (descriptively but unimaginatively) MozReview, is
ready for general use.
In the interests of beta-testing our documentation at the same time as
our code, I want to mostly confine my post to a link to our docs:
http://mozilla-version-control
, now named (descriptively but unimaginatively) MozReview, is
ready for general use.
In the interests of beta-testing our documentation at the same time as
our code, I want to mostly confine my post to a link to our docs:
http://mozilla-version-control-tools.readthedocs.org/en/latest
-review tool based on Review Board. I'm excited to announce that
this tool, now named (descriptively but unimaginatively) MozReview, is
ready for general use.
In the interests of beta-testing our documentation at the same time as
our code, I want to mostly confine my post to a link to our docs
excited to announce that
this tool, now named (descriptively but unimaginatively) MozReview, is
ready for general use.
In the interests of beta-testing our documentation at the same time as
our code, I want to mostly confine my post to a link to our docs:
http://mozilla-version-control
On 11/9/14 8:29 PM, Boris Zbarsky wrote:
On 11/9/14, 11:10 PM, Gregory Szorc wrote:
We currently only attempt to map each review/commit series to a single
bug.
This is definitely a problem; it serializes workflow such that you have
to get review on bug 1 and land it before you can even
On 11/10/14, 12:14 PM, Gregory Szorc wrote:
I think if we land support for specifying the base revision to review
(currently it takes all non-public changesets up to the revision you
specify or . if none), that will be a sufficient stop-gap until proper
multi-bug support is implemented.
Yes,
. I'm excited to announce that
this tool, now named (descriptively but unimaginatively) MozReview, is
ready for general use.
In the interests of beta-testing our documentation at the same time as
our code, I want to mostly confine my post to a link to our docs:
http://mozilla-version-control
.
On Wed, Nov 5, 2014 at 11:50 PM, Mark Côté mc...@mozilla.com wrote:
A couple months ago I gave a sneak peak into our new repository-based
code-review tool based on Review Board. I'm excited to announce that
this tool, now named (descriptively but unimaginatively) MozReview, is
ready for general
On 11/9/14, 11:10 PM, Gregory Szorc wrote:
We currently only attempt to map each review/commit series to a single bug.
This is definitely a problem; it serializes workflow such that you have
to get review on bug 1 and land it before you can even request review on
bug 2 that depends on bug 1,
on Review Board. I'm excited to announce that
this tool, now named (descriptively but unimaginatively) MozReview, is
ready for general use.
In the interests of beta-testing our documentation at the same time as
our code, I want to mostly confine my post to a link to our docs:
http://mozilla
:50 PM, Mark Côté mc...@mozilla.com wrote:
A couple months ago I gave a sneak peak into our new repository-based
code-review tool based on Review Board. I'm excited to announce that
this tool, now named (descriptively but unimaginatively) MozReview, is
ready for general use.
In the interests
A couple months ago I gave a sneak peak into our new repository-based
code-review tool based on Review Board. I'm excited to announce that
this tool, now named (descriptively but unimaginatively) MozReview, is
ready for general use.
In the interests of beta-testing our documentation at the same
17 matches
Mail list logo
