New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add patchbot to the developers guide #10702
Comments
Author: Marco Streng |
Changed keywords from none to patchbot, buildbot, bot, trac, developers guide |
Reviewer: André Apitzsch |
comment:2
It looks good to me. |
comment:3
Marco: please fix the commit message of your patch (use hg qrefresh -e for that). |
Attachment: trac_10702-patchbot-doc.patch.gz |
comment:4
What do you mean by "fix"? Is it ok now? That was a lot of work for just removing "[mq]: " (of which I don't know where it came from or what it means). |
comment:5
Replying to @mstreng:
Yes, it looks okay now. The [mq] stands for "Mercurial queue". By default the commit message comes from the argument to Why was it a lot of work, what did you do? |
comment:6
Replying to @jdemeyer:
log in to a machine that has Sage, copy patch location, hg qimport, hg qapply, hg qrefresh -e, remove "[mq]: " from the commit message, hg export, copy patch to office pc, log in to trac, upload patch, tick needs_review, click Submit All that to remove four characters from a commit message. Why couldn't I just edit the patch to remove those 4 characters? Would it have screwed up some kind of checksum? |
Merged: sage-4.6.2.alpha4 |
Add a link to the patchbot wiki in the developers guide (see this thread).
CC: @jdemeyer
Component: documentation
Keywords: patchbot, buildbot, bot, trac, developers guide
Author: Marco Streng
Reviewer: André Apitzsch
Merged: sage-4.6.2.alpha4
Issue created by migration from https://trac.sagemath.org/ticket/10702
The text was updated successfully, but these errors were encountered: