From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: Patch(es) committing - (stupid) question
Date: Wed, 04 Sep 2013 22:28:42 +0200 [thread overview]
Message-ID: <522797FA.8090308@gmail.com> (raw)
In-Reply-To: <5227816A.70803@volny.cz>
[-- Attachment #1: Type: text/plain, Size: 1395 bytes --]
On 04.09.2013 20:52, Aleš Nesrsta wrote:
> Hi,
>
> I have stupid question related to organization of committing of patches
> - I am currently little bit confused.
>
Sorry for not responding, I have a neural learning paper I have to hand
in shortly which is very important. I'll stay mostly inactive until 12th
of September.
> Vladimir wrote to me in some latest e-mail :
> "I don't see any messages in my mailbox from you tagged as pending
> patches."
>
> And, additionally, I see only Vladimir's commits in trunk ChangeLog in
> the last time.
>
> I.e. it looks for me like something changed here in the meantime and I
> missed it - maybe only Vladimir can commit patch(es) and I should ask
> him in some (for me currently unknown) way - ?
>
> So, my question is:
> How should I correctly ask commit of my patch(es) into trunk?
>
> (Question is not related to BZR procedure, only to development
> organization - how to ask commit of patch or how to get permission to do
> commit myself, if it is still possible.)
>
> Sorry if it is written somewhere on GRUB web-pages - but for the first
> look I don't see any related information how the GRUB development is
> organized.
>
> BR,
> Ales
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 291 bytes --]
prev parent reply other threads:[~2013-09-04 20:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-04 18:52 Patch(es) committing - (stupid) question Aleš Nesrsta
2013-09-04 20:28 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=522797FA.8090308@gmail.com \
--to=phcoder@gmail.com \
--cc=grub-devel@gnu.org \
/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.
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 NNTP newsgroup(s).