Also, if you did the double self-update to move over to pip while
running under pyenv, moz-phab may suddenly disappear from your path
until you restart your shell.
Dan
Am Do., 24. Okt. 2019 um 03:55 Uhr schrieb Axel Hecht :
>
> Am 24.10.19 um 12:13 schrieb Henrik Skupin:
> > glob wrote on 23.10.1
Am 24.10.19 um 12:13 schrieb Henrik Skupin:
glob wrote on 23.10.19 17:56:
It's available now - make sure you're running the latest version by
running `moz-phab self-update`.
That's what I did yesterday, but as it looks like the self-update
actually didn't update my version to the latest MozPh
Emilio and Emma brings up an important barrier to outside contribution
here.
Also sprach Emilio Cobos Álvarez:
> On 10/23/19 10:24 PM, Emma Humphries wrote:
>> Will this make it easier for non-staff contributors to get their change
>> sets reviewed and landed?
>> What else should we be doing for
glob wrote on 23.10.19 17:56:
> It's available now - make sure you're running the latest version by
> running `moz-phab self-update`.
That's what I did yesterday, but as it looks like the self-update
actually didn't update my version to the latest MozPhab-0.1.55. I will
check soon with this versi
Likewise I use `phlay` on git.
On Wed, Oct 23, 2019 at 1:35 PM Jörg Knobloch wrote:
> On 23 Oct 2019 22:24, Emma Humphries wrote:
> > Will this make it easier for non-staff contributors to get their change
> > sets reviewed and landed?
> >
> > What else should we be doing for that.
> >
> > I hav
On 23 Oct 2019 22:24, Emma Humphries wrote:
Will this make it easier for non-staff contributors to get their change
sets reviewed and landed?
What else should we be doing for that.
I have some ideas I'm working on for views in Bugzilla to help with that so
that contributors can see what's going
On 10/23/19 10:24 PM, Emma Humphries wrote:
Will this make it easier for non-staff contributors to get their change
sets reviewed and landed?
What else should we be doing for that.
I have some ideas I'm working on for views in Bugzilla to help with that so
that contributors can see what's going
Will this make it easier for non-staff contributors to get their change
sets reviewed and landed?
What else should we be doing for that.
I have some ideas I'm working on for views in Bugzilla to help with that so
that contributors can see what's going on, and where they can take action
to help.
It's available now - make sure you're running the latest version by
running `moz-phab self-update`.
-glob
Henrik Skupin wrote on 23/10/19 11:49 pm:
Piotr Zalewa wrote on 22.10.19 17:25:
Since today MozPhab does not require Arcanist to submit patches in all
supported VCS's. It's an optional
Piotr Zalewa wrote on 22.10.19 17:25:
> Since today MozPhab does not require Arcanist to submit patches in all
> supported VCS's. It's an optional and experimental feature. Add the
> `--no-arc` option to switch it on.
Great to hear, but is there also an ETA when this mode will be available
for us
This is great, thank you zalun!
moz-phab has improved by leaps and bounds over the last few months. Great
job to you and the team hacking on it - it's a critical part of my toolset.
On Tue, 22 Oct 2019 at 11:26, Piotr Zalewa wrote:
> Hi all,
>
> Since today MozPhab does not require Arcanist to
Hi all,
Since today MozPhab does not require Arcanist to submit patches in all
supported VCS's. It's an optional and experimental feature. Add the
`--no-arc` option to switch it on.
Feel free to use it and report any bugs the usual way -
https://bugzilla.mozilla.org/enter_bug.cgi?product=Conduit&
12 matches
Mail list logo
