From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 2/2] docs/manual: patches that change files with spaces in the name
Date: Sun, 24 Jan 2016 22:08:06 +0100 [thread overview]
Message-ID: <20160124210806.GG3405@free.fr> (raw)
In-Reply-To: <56a5389a95e45_611f13d281c87bf@ultri2.mail>
Ricardo, All,
On 2016-01-24 18:48 -0200, Ricardo Martincoski spake thusly:
> Arnout, Yann E. MORIN,
>
> On Sun, Jan 24, 2016 at 02:20 PM, Yann E. MORIN <yann.morin.1998@free.fr> wrote:
> [snip]
> >> - Arnout suggested to drop the patch to the manual:
> >> "I think that this situation is so exotic that it doesn't warrant a
> >> mention in the manual. The manual is already long and complicated
> >> enough."
> >> I updated the manual for now because it is a separate patch that can
> >> be Rejected if others agree with Arnout.
> >
> > Well, like Arnout said, the number of cases that this would bite us is
> > very limited (as in: there is only one case).
> >
> > The most problematic issue here is not doing the fix, but recognising
> > the symptoms. This is such a rare occurence that I'm afraid we'll again
> > scratch our heads when we next encounter this issue. That is, if there's
> > ever a "next time"...
> >
> > So I don't think it is necessary that the manual has a blurb about that.
> [snip]
>
> Thank you both for your time.
> I will set this patch as Rejected.
>
> All,
>
> I guess I don't need to send a v4 for the series (now it became a
> single patch) while no change is requested in
> http://patchwork.ozlabs.org/patch/572263/
> If someone disagrees, just let me know and I will send it.
Indeed, no need to resubmit.
Thanmks! :-)
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
prev parent reply other threads:[~2016-01-24 21:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-24 13:19 [Buildroot] [PATCH v3 0/2] fix build using old versions of patch Ricardo Martincoski
2016-01-24 13:19 ` [Buildroot] [PATCH v3 1/2] package/libsoil: " Ricardo Martincoski
2016-01-24 14:31 ` Arnout Vandecappelle
2016-01-25 22:35 ` Thomas Petazzoni
2016-02-20 22:26 ` Peter Korsgaard
2016-01-24 13:19 ` [Buildroot] [PATCH v3 2/2] docs/manual: patches that change files with spaces in the name Ricardo Martincoski
2016-01-24 16:20 ` Yann E. MORIN
2016-01-24 20:48 ` Ricardo Martincoski
2016-01-24 21:08 ` Yann E. MORIN [this message]
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=20160124210806.GG3405@free.fr \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/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.