public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: "Benoît Thébaudeau" <benoit.thebaudeau@advansee.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 1/9] FAT: cosmetic: Remove extra spaces
Date: Sun, 12 Aug 2012 23:07:31 +0200 (CEST)	[thread overview]
Message-ID: <987616329.2335426.1344805651332.JavaMail.root@advansee.com> (raw)
In-Reply-To: <20120812204218.378A6202A85@gemini.denx.de>

Dear Wolfgang Denk,

> Dear =?utf-8?Q?Beno=C3=AEt_Th=C3=A9baudeau?=,
> 
> you wrote:
> > 
> > > > > If it's ack'ed, why does nobody apply it? What is the normal
> > > > > life cycle of
> > > > > patches like these that don't have a custodian?
> 
> And I explained to you:
> 
> > They end on my table, and probably get merged when the next merge
> > window opens.  See http://www.denx.de/wiki/U-Boot/ReleaseCycle
> 
> But you continue to ask again and again and again:
> 
> > > > Can you apply it now that the merge window is open?
> > ...
> > > Can someone answer, please?
> > >
> > Do you have any idea why nobody applies this series and answers?
> > Who is the fs
> > custodian? Wolfgang since I can't find a custodian defined for fs,
> > no? Is it
> > because of vacations or something? I'd like if this series could be
> > applied
> > before the end of the current merge window.
> 
> Didn't I tell you that these will be handled by me? The when depends
> on when I find time to do this.  I have a lot of patches on my stack,
> and usually I process these sequentially, and not in the order of the
> "priority" as the submitter wants to assign.  It is perfectly OK to
> send a reminder when there is nothing happening, or when the merge
> window closes and I call for unprecessed patches to be flagged, but
> frankly, you ask a bit too often.  You may want to read
> http://www.catb.org/~esr/faqs/smart-questions.html#urgent ...

Understood. Sorry for the noise. I'm still new to U-Boot mailing list, so I'm
learning the rules and timings progressively. I was not asking for priority over
others. It's just that you said you handled such patches when the next merge
window opens, but then nothing happened when the merge window opened, even after
a few weeks, so I was wondering why. Now it's clear.

Best regards,
Beno?t

  reply	other threads:[~2012-08-12 21:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-20 13:18 [U-Boot] [PATCH v2 1/9] FAT: cosmetic: Remove extra spaces Benoît Thébaudeau
2012-07-20 13:24 ` Benoît Thébaudeau
2012-07-21 17:23 ` Mike Frysinger
2012-07-27 14:21   ` Benoît Thébaudeau
2012-07-27 14:29     ` Wolfgang Denk
2012-08-03 23:11       ` Benoît Thébaudeau
2012-08-10 14:41         ` Benoît Thébaudeau
2012-08-11 20:32           ` Benoît Thébaudeau
     [not found]             ` <CALButC+R2h9g=ZBDi0mV4JfywmXpWzswhNEirfh73aPp+tk_Ow@mail.gmail.com>
2012-08-11 21:43               ` [U-Boot] Fwd: " Graeme Russ
2012-08-11 22:03                 ` [U-Boot] " Benoît Thébaudeau
2012-08-12 21:01                   ` Wolfgang Denk
2012-08-12 20:42             ` Wolfgang Denk
2012-08-12 21:07               ` Benoît Thébaudeau [this message]
2012-09-02 15:13 ` Wolfgang Denk

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=987616329.2335426.1344805651332.JavaMail.root@advansee.com \
    --to=benoit.thebaudeau@advansee.com \
    --cc=u-boot@lists.denx.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox