From: Mike Zick <minimod@morethan.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] libFTDI major version update 1. This version can coexists beside the 0.x version (libftdi.so, libftdi1.so).
Date: Thu, 2 Oct 2014 07:45:33 -0500 [thread overview]
Message-ID: <20141002074533.1ece2b48@core2quad.morethan.org> (raw)
In-Reply-To: <2.c5a9d6940ebdbeb712d0@polarstar>
On Thu, 02 Oct 2014 09:52:10 +0200
daniel.sangue at sangue.ch wrote:
> Give me some time because i havent a working smtp-server connection
> at work. And i can not do an incremental patch - because i have
> deleted the copy of the repo where the patch was based on. I only can
> create a new patch and take your proposed git message for it. Is this
> ok for you or what should i do now?
>
As a long time M.L. reader, (not a reviewer) I feel safe in answering
this one. ;)
The comments made where scattered throughout your submission, so I
don't think that your having to re-generate a new one will make
very much difference.
That is not what you would want to do to fix a single line "Oops"
of course, but in this case, it should be ok.
Just be sure to include the [PATCH V2 ... etc in the new title
and a comment about V1 -> V2 changes made.
Mike
>
> Greets Dani
next prev parent reply other threads:[~2014-10-02 12:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-02 7:52 [Buildroot] [PATCH 1/1] libFTDI major version update 1. This version can coexists beside the 0.x version (libftdi.so, libftdi1.so) daniel.sangue at sangue.ch
2014-10-02 12:45 ` Mike Zick [this message]
2014-10-02 12:56 ` Mike Zick
2014-10-03 13:02 ` Thomas Petazzoni
-- strict thread matches above, loose matches on Subject: below --
2014-10-01 14:18 Daniel Sangue
2014-10-01 14:45 ` Thomas Petazzoni
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=20141002074533.1ece2b48@core2quad.morethan.org \
--to=minimod@morethan.org \
--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.