All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Grandegger <wg@grandegger.com>
To: Oliver Hartkopp <socketcan@hartkopp.net>
Cc: Marc Kleine-Budde <mkl@pengutronix.de>,
	"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: Re: [PATCH 0/6] CAN FD support
Date: Tue, 19 Jun 2012 09:26:11 +0200	[thread overview]
Message-ID: <4FE02993.7040208@grandegger.com> (raw)
In-Reply-To: <4FDF7E10.9050301@hartkopp.net>

On 06/18/2012 09:14 PM, Oliver Hartkopp wrote:
> On 18.06.2012 21:10, Marc Kleine-Budde wrote:
> 
>> On 06/18/2012 07:38 PM, Oliver Hartkopp wrote:
>>> Hello Marc,
>>>
>>> here's my first real git patch series adding support for CAN with flexible
>>> data rate (CAN FD).
>>>
>>> As there were no new remarks to my RFC v5 from 2012-05-28
>>>
>>> http://comments.gmane.org/gmane.linux.can/1297
>>>
>>> and it's tested and running on my machine for a while now it's IMHO time
>>> for net-next now.
>>>
>>> You can also pull the series ;-)
>>
>> I can pull, but David want's to have a clean tree. So I have to pull and
>> rebase it on my tree.
> 
> 
> I created a branch 'canfd' on a clone of *your* can-next.
> 
> What's not clean there?
> 
> You can pull Daves net-next and then pull the canfd branch, right?
> 
>>
>>> Git is hard for newbies but i gave my very best ...
>>
>> Once you can use it, you don't want to code without it.
> 
> 
> Yes -  it's getting better. Indeed it looks like Thunderbird mangles the mails
> when editing the draft mails.

I use the "Toggle Word Wrap" Extension to avoid white space mangling
with Thunderbird and sometimes I even use it to send single patches.
Anyway, especially for a series of patches, "git send-email" is the
better choice.

Wolfgang.


      parent reply	other threads:[~2012-06-19  7:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-18 17:38 [PATCH 0/6] CAN FD support Oliver Hartkopp
2012-06-18 19:10 ` Marc Kleine-Budde
2012-06-18 19:14   ` Oliver Hartkopp
2012-06-18 19:27     ` Marc Kleine-Budde
2012-06-18 19:30       ` Oliver Hartkopp
2012-06-18 19:38         ` Marc Kleine-Budde
2012-06-19  7:26     ` Wolfgang Grandegger [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=4FE02993.7040208@grandegger.com \
    --to=wg@grandegger.com \
    --cc=linux-can@vger.kernel.org \
    --cc=mkl@pengutronix.de \
    --cc=socketcan@hartkopp.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.