From: Alexander Aring <alex.aring@gmail.com>
To: Michel Stam <michel@reverze.net>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: [PATCH 2/3] x86: Add support for IDE on the legacy I/O ports
Date: Sat, 5 Apr 2014 08:58:49 +0200 [thread overview]
Message-ID: <20140405065848.GA1413@omega.Speedport_W_921V_1_24_000> (raw)
In-Reply-To: <E97972E6-F8B1-438A-8BEE-F48CF896908F@reverze.net>
On Sat, Apr 05, 2014 at 08:56:25AM +0200, Michel Stam wrote:
> Hello Alex,
>
> I think we misunderstood eachother; I was talking about space changes in .c files caused by an editor. send-email came after the editing.
>
> Reading back I think you were talking about directly editing patches, which I did not do.
>
> The patches as they were sent to this list are the immediate result/output of the git send-email command, if theres inconsistencies in the patch file itself I have no explanation for that.
ok, but then I don't unerstand why it is " +#..." instead "+ #..." the +
comming from diff and should always at the beginnen of line.
I think we should stop this discussion now. Nevertheless I saw there is
already a v2. :-)
- Alex
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2014-04-05 6:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-25 11:12 Michel Stam
2014-04-05 3:11 ` Jean-Christophe PLAGNIOL-VILLARD
2014-04-05 6:36 ` Michel Stam
2014-04-05 5:01 ` Alexander Aring
2014-04-05 6:39 ` Michel Stam
2014-04-05 6:45 ` Alexander Aring
2014-04-05 6:56 ` Michel Stam
2014-04-05 6:58 ` Alexander Aring [this message]
2014-04-05 7:12 ` Michel Stam
2014-04-05 7:18 ` Alexander Aring
2014-04-05 7:20 ` Michel Stam
2014-04-05 7:21 ` Alexander Aring
2014-04-04 13:41 [PATCH 1/3] common: Allow for I/O mapped I/O michel
2014-04-04 13:41 ` [PATCH 2/3] x86: Add support for IDE on the legacy I/O ports michel
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=20140405065848.GA1413@omega.Speedport_W_921V_1_24_000 \
--to=alex.aring@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=michel@reverze.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox