From: Marcin Borkowski <mbork@mbork.pl>
To: Phillip Lord <phillip.lord@russet.org.uk>
Cc: emacs-devel@gnu.org
Subject: Re: A problem with old bugs
Date: Tue, 07 Mar 2017 07:16:38 +0100 [thread overview]
Message-ID: <87innl627t.fsf@jane> (raw)
In-Reply-To: <87y3wio83o.fsf@russet.org.uk>
On 2017-03-06, at 14:19, Phillip Lord <phillip.lord@russet.org.uk> wrote:
> Marcin Borkowski <mbork@mbork.pl> writes:
>>> If not (no write privs), why not? What are you waiting for?
>>
>> Nobody gave them to me.
>>
>> What should be the workflow once I have them? I assume that I branch
>> off fresh master, push my branch and write here - correct?
>
>
> Emacs doesn't have a well developed branch merge workflow. In general,
> people push things straight onto master. If you are unsure whether your
> patch is good, then asking on emacs-devel, then no one complaining for a
> while is probably a good sign.
That's interesting. I'd be a bit afraid of pushing to master, if only
because I have a habit of compiling Emacs from master from time to
time...
> At the end of the day, try and get it right, but breaking Emacs is going
> to happen and it's not a disaster. I've done it lots recently!
;-)
> Phil
Thanks,
--
Marcin Borkowski
next prev parent reply other threads:[~2017-03-07 6:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-01 8:22 A problem with old bugs Marcin Borkowski
2017-03-01 10:26 ` Thien-Thi Nguyen
2017-03-01 13:28 ` Marcin Borkowski
2017-03-02 7:38 ` Thien-Thi Nguyen
2017-03-02 12:33 ` Noam Postavsky
2017-03-02 16:53 ` Richard Stallman
2017-03-07 6:17 ` Marcin Borkowski
2017-03-06 13:19 ` Phillip Lord
2017-03-07 6:16 ` Marcin Borkowski [this message]
2017-03-07 12:24 ` Phillip Lord
2017-03-01 16:16 ` Eli Zaretskii
2017-03-07 6:15 ` Marcin Borkowski
2017-03-07 16:51 ` Eli Zaretskii
2017-03-08 7:01 ` Marcin Borkowski
2017-03-08 16:08 ` Eli Zaretskii
2017-05-21 16:00 ` John Wiegley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87innl627t.fsf@jane \
--to=mbork@mbork.pl \
--cc=emacs-devel@gnu.org \
--cc=phillip.lord@russet.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).