From: Marco Gerards <mgerards@xs4all.nl>
To: Thomas Schwinge <tschwinge@gnu.org>
Cc: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Update for NTFS file system driver
Date: Sun, 10 Jun 2007 11:55:07 +0200 [thread overview]
Message-ID: <87ps4416dg.fsf@xs4all.nl> (raw)
In-Reply-To: <20070610091937.GE29831@fencepost.gnu.org> (Thomas Schwinge's message of "Sun, 10 Jun 2007 11:19:37 +0200")
Thomas Schwinge <tschwinge@gnu.org> writes:
> Hello!
>
> On Sun, Jun 10, 2007 at 09:57:44AM +0200, Marco Gerards wrote:
>> Bean <bean123@126.com> writes:
>> > On Sat, Jun 09, 2007 at 08:05:45PM +0200, Marco Gerards wrote:
>> >> The normal procedure for patches is to make them consistent with the
>> >> GCS (GNU Coding Standards), include a changelog. That way it is
>> >> easier to review the patch and to include it in GRUB 2.
>>
>> The GNU Coding Standards:
>> http://www.gnu.org/prep/standards/standards.html
>>
>> The specific part on ChangeLog entries:
>> http://www.gnu.org/prep/standards/standards.html#Change-Logs
>>
>> The biggest part is on indentation, etc.
>
> Sorry, but that is also the part which the upstream committers (e.g. you,
> or me, or some more others) can trivially fix if you don't like it the
> way the first-time contributor has done. That's my idea of this eternal
> ``your-formatting-only-does-stop-us-from-committing-your-patch'' thing.
> And that is also what I would expect if I were a first-time contributor.
> Otherwise I might decide to spend my time elsewhere.
The problem is, as you may know, that we have very little time to
clean up all the patches. But I am certainly willing to help people
wherever possible with these kind of tasks. Besides that, for my
feeling the coding style is part of the job.
But if you do have the time, please help us out!
--
Marco
next prev parent reply other threads:[~2007-06-10 9:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-09 4:56 Update for NTFS file system driver Bean
2007-06-09 18:05 ` Marco Gerards
2007-06-10 3:42 ` Bean
2007-06-10 7:57 ` Marco Gerards
2007-06-10 9:19 ` Thomas Schwinge
2007-06-10 9:55 ` Marco Gerards [this message]
2007-06-10 12:03 ` Bean
2007-06-10 15:15 ` Robert Millan
2007-06-10 15:29 ` Marco Gerards
2007-06-10 16:36 ` Bean
2007-06-13 18:27 ` Marco Gerards
2007-06-10 10:18 ` history of fsys_ntfs.c (Re: Update for NTFS file system driver) Robert Millan
2007-06-10 10:52 ` Bean
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=87ps4416dg.fsf@xs4all.nl \
--to=mgerards@xs4all.nl \
--cc=grub-devel@gnu.org \
--cc=tschwinge@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.