From: Vladimir Testov <vladimir.testov@rosalab.ru>
To: grub-devel@gnu.org
Subject: 15 Patches, which aren't commented or accepted yet
Date: Fri, 26 Apr 2013 17:54:06 +0400 [thread overview]
Message-ID: <1473558.NjSsOkerik@icedphoenix> (raw)
Hello again!
I write this letter only for purpose of combining information in one place and
to make sure the patches I wrote weren't lost or forgotten.
So, you can close this message if you don't need this information.
1 (from March, 27)
[PATCH][BUGFIX] wrong determination of first printed entry in some cases
http://lists.gnu.org/archive/html/grub-devel/2013-03/msg00112.html
2-11
[gfxmenu/list] patches (except 9th)
12-15
4 new patches:
-start_angle patch
-documentation update
-remove outdated code
-terminal window moving options
and unresolved question about multistring support:
I can't make it work with existing line-breaking mechanism and need some help
to understand why.
Thanks to all!
--
With best regards,
_______________________________
Vladimir Testov, ROSA Laboratory.
www.rosalab.ru
next reply other threads:[~2013-04-26 13:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 13:54 Vladimir Testov [this message]
2013-04-28 11:18 ` 15 Patches, which aren't commented or accepted yet Vladimir 'φ-coder/phcoder' Serbinenko
2013-04-29 9:00 ` Vladimir Testov
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=1473558.NjSsOkerik@icedphoenix \
--to=vladimir.testov@rosalab.ru \
--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.