All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: gettext: normal_menu.c
Date: Sun, 29 Nov 2009 02:17:48 +0100	[thread overview]
Message-ID: <4B11CBBC.5020707@gmail.com> (raw)
In-Reply-To: <20091129010454.GA10367@pina.cat>

[-- Attachment #1: Type: text/plain, Size: 1711 bytes --]

Carles Pina i Estany wrote:
> Hello,
>
> On Nov/28/2009, Robert Millan wrote:
>   
>> Please remember about spaces in our coding style:
>>
>> On Sat, Nov 28, 2009 at 12:21:28PM +0000, Carles Pina i Estany wrote:
>>     
>>> +      next_new_line = (grub_uint32_t*)last_position;
>>>       
>>                                        ^ ^
>>     
>>> +      while (getstringwidth(current_position,next_new_line) > line_len 
>>>       
>>                               ^                 ^
>> etc.  If in doubt, use indent(1).
>>     
>
> Attached the new patch. Comments are welcomed.
>
> The original normal/* files are not indent consistent. So I:
> 1.- copied the files to old/
> 2.- applied the patch to the original files and copy to new/
> 3.- indent old/* and new/*
> 4.- diff -p -u old/ new/
>
> For next time: what you think to make a patch + ChangeLog entry and
> push to trunk and then another push with the changes to the
> indent-compliant files?
>
>   
If you find badly-indented files and you know nobody else is working on
those files right now (e.g. no changes on it in experimental) you can
indent them in the trunk without mentionning it on the list. If you're
aware of people working on these files notify them. Also check that
indent didn't make the things worse and add a Changlog entry like
YYYY-MM-DD  .....

          * <file>: Indented.
> Cheers,
>
>   
> ------------------------------------------------------------------------
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel


-- 
Regards
Vladimir 'φ-coder/phcoder' Serbinenko



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 293 bytes --]

  reply	other threads:[~2009-11-29  1:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-28  0:09 gettext: normal_menu.c Carles Pina i Estany
2009-11-28  1:24 ` Carles Pina i Estany
2009-11-28  1:47   ` Carles Pina i Estany
2009-11-28 12:21     ` Carles Pina i Estany
2009-11-28 19:09       ` Robert Millan
2009-11-29  1:04         ` Carles Pina i Estany
2009-11-29  1:17           ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2009-12-03 23:22           ` Carles Pina i Estany

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=4B11CBBC.5020707@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 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.