All of lore.kernel.org
 help / color / mirror / Atom feed
From: phcoder <phcoder@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] FAT, UFS and mtime
Date: Sun, 01 Mar 2009 22:17:17 +0100	[thread overview]
Message-ID: <49AAFB5D.8060007@gmail.com> (raw)
In-Reply-To: <ca0f59980903011113i2744f417ud5e805a835283c80@mail.gmail.com>

Bean wrote:
> On Mon, Mar 2, 2009 at 12:25 AM, phcoder <phcoder@gmail.com> wrote:
>> Hello all. It seems that gcc has trouble with -m32 when structure is passed
>> as argument. So I replaced that part by a pointer. Also I made some
>> improvements to ufs code to support solaris branch of ufs. I tested it also
>> with freebsd and netbsd's branch and it works fine on it too.
>> As my 3 FS patches: mtime, FAT and UFS are interdependent I submit a patch
>> with all 3 features. If it's really necessary I can split them but it
>> requires a lot of unnecessary work
> 
> Hi,
> 
> Please don't merge patch, it makes it harder to track down bugs later.
>
Actually these patches aren't merged. The problem is that my copyright 
assignment hasn't been signed by FSF yet so uncommited patches 
accumulate in my grub2 tree

 >
> Also, perhaps you should keep datetime.c as it is. I'm planning to
> split the normal mode into separate components, it'd be nice if you
> don't add files to the normal directory.
> 
Feel free to put datetime.c wherever you want

-- 

Regards
Vladimir 'phcoder' Serbinenko



  reply	other threads:[~2009-03-01 21:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-01 16:25 [PATCH] FAT, UFS and mtime phcoder
2009-03-01 19:13 ` Bean
2009-03-01 21:17   ` phcoder [this message]
2009-03-02  3:58     ` Bean
2009-03-02  4:39       ` Pavel Roskin
2009-03-11 21:32 ` phcoder
2009-03-11 22:16   ` phcoder
2009-03-13 19:10 ` Robert Millan
2009-03-15  0:34   ` phcoder
2009-04-04  9:21     ` phcoder
2009-04-05 14:38       ` Yoshinori K. Okuji
2009-03-15 11:16   ` phcoder

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=49AAFB5D.8060007@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.