From: "Aleš Nesrsta" <starous@volny.cz>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Patch(es) committing - (stupid) question
Date: Wed, 04 Sep 2013 20:52:26 +0200 [thread overview]
Message-ID: <5227816A.70803@volny.cz> (raw)
Hi,
I have stupid question related to organization of committing of patches
- I am currently little bit confused.
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
next reply other threads:[~2013-09-04 18:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-04 18:52 Aleš Nesrsta [this message]
2013-09-04 20:28 ` Patch(es) committing - (stupid) question Vladimir 'φ-coder/phcoder' Serbinenko
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=5227816A.70803@volny.cz \
--to=starous@volny.cz \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.