Dear all,
I'm prod to announce that MathJaX 2.3 has been released this Monday
and successfully integrated to the Wikimedia Math extension by the
MathJax developer Frédéric Wang.
In the past month Gabriel Wicke, Frédéric Wang and me have been
working on a new version of the Math extension that
Hello,
Today at 9am UTC, I started upgrading Zuul to a version that uses
Gearman to trigger jobs (and fix a bunch of issues). The upgrade had to
be cancelled, service got disrupted for an hour.
The Zuul code upgrade itself went well and was completed in half an hour
at 9:30am UTC.
Timo
Currently I do:
* clone a repo
* setup git hooks
# patch 1:
* apply my changes
* commit
* execute git-review
# patch 2:
* apply my changes
* commit
FAIL - the new commit it depending on previous commit - I can't push
What am I supposed to do in order to push multiple separate patches?
Normally:
* clone a repo
* setup git hooks
# patch 1:
* git checkout -b some_branch_name
* apply my changes
* git commit -a
* git review
# patch 2:
* git checkout production (or master on non-puppet repositories)
* git pull
* git checkout -b some_other_branch_name
* apply my changes
* git
petanb@srv:~/puppet/modules/toollabs/manifests$ git checkout production
Already on 'production'
Your branch is ahead of 'origin/production' by 2 commits.
this keep my change depending on previous commit ^ and FAIL again
On Wed, Nov 20, 2013 at 2:19 PM, Nikolas Everett never...@wikimedia.org
if I do this I get
- patch1
-- patch 2 (depends on patch1)
in gerrit. What I need is, to make 2 patches that are completely unrelated
On Wed, Nov 20, 2013 at 2:50 PM, Petr Bena benap...@gmail.com wrote:
petanb@srv:~/puppet/modules/toollabs/manifests$ git checkout production
Already on
aha I see now, I should have branch before patch1. I didn't. What am I
supposed to do now?
On Wed, Nov 20, 2013 at 2:19 PM, Nikolas Everett never...@wikimedia.org wrote:
Normally:
* clone a repo
* setup git hooks
# patch 1:
* git checkout -b some_branch_name
* apply my changes
* git
I used my favorite command
rm -rf repository git clone again
so it's fixed for now, but it would be cool to know how to fix that anyway
On Wed, Nov 20, 2013 at 2:55 PM, Petr Bena benap...@gmail.com wrote:
aha I see now, I should have branch before patch1. I didn't. What am I
supposed to do
when I did a new branch before git-review it now show this as topic
in gerrit: https://gerrit.wikimedia.org/r/#/c/96484/
will it merge this to production branch?
On Wed, Nov 20, 2013 at 2:59 PM, Bartosz Dziewoński matma@gmail.com wrote:
On Wed, 20 Nov 2013 14:50:55 +0100, Petr Bena
On Wed, Nov 20, 2013 at 9:01 AM, Petr Bena benap...@gmail.com wrote:
when I did a new branch before git-review it now show this as topic
in gerrit: https://gerrit.wikimedia.org/r/#/c/96484/
will it merge this to production branch?
Yes.
___
Hi,
On Wed, Nov 20, 2013 at 02:56:44PM +0100, Petr Bena wrote:
I used my favorite command
rm -rf repository git clone again
so it's fixed for now, but it would be cool to know how to fix that anyway
Assuming
* you are on branch production,
* production branch does no longer point to
On 11/20/13 7:13 AM, Petr Bena wrote:
snip
What am I supposed to do in order to push multiple separate patches?
The short answer is: If you're working on two unrelated things, do them
on separate branches.
If you /already/ have two patches on the same branch and realize you
want to split
Wednesday, November 20, 2013 at 10:00 PM UTC at #wikimedia-meetbot
Today we discussed three RFCs:
* Page deletion
* Configuration database 2
* Text extraction
Check the meeting notes and the full logs at
https://www.mediawiki.org/wiki/Architecture_meetings/RFC_review_2013-11-20
Propose your
As folks may be aware, over in the Wikimedia Mobile Apps team we're
starting a refresh of the Wikipedia mobile apps for Android and iOS, which
have not been updated in a while and are now wayyy behind the mobile web in
features and UI awesomeness.
The new apps are using native UI around the
14 matches
Mail list logo
