All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Michael Haberler <haberlerm@gmail.com>
Cc: xenomai <xenomai@xenomai.org>
Subject: Re: [Xenomai] RT-CAN driver for C_CAN,D_CAN cores ready
Date: Wed, 29 Apr 2015 06:30:26 +0200	[thread overview]
Message-ID: <20150429043026.GI1993@hermes.click-hack.org> (raw)
In-Reply-To: <6EE509AA-B0D3-40DC-9DEA-63E1DCDB39A6@gmail.com>

On Tue, Apr 28, 2015 at 10:19:26PM +0200, Michael Haberler wrote:
> Gille -
> 
> > Am 28.04.2015 um 18:02 schrieb Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>:
> > 
> > On Tue, Apr 28, 2015 at 05:47:40PM +0200, Michael Haberler wrote:
> >> as requested:
> > 
> > This is a mess, really, you add files to remove them later.
> 
> Steve started with the vanilla c_can driver, copied and renamed the files. But the code still shares a lot with the original.
> 
> I do think history is important - when searching for a bug this driver introduced, or backporting a fix to the vanilla driver.
> 
> This is why you see what you see. I think it is more relevant than aesthetics.
> 
> If you prefer to have a history-free squash, that is fine too - I pity the fellow trying to nail a bug though. Please advise.

The diff which renames the files contains absolutely no valuable
information:

- if the files were just renamed, then it contains a lot of lines
for just a few rename commands, and you can make this patch
disappear in the git history, simply starting with files with the
right names, and not loose any relevant information (I do not see
what the information that the file was named c_can.c then renamed
rtc_can.c brings to someone looking for a bug); 

- if the files were both renamed and modified by this commit, the
information about what was modified is lost, because the diff
contains a file removal and a file addition, not the crucial
difference between the two files.

> 
> > 
> > A patch should be against Xenomai sources, and for adding a driver
> > it should only add file or modify existing files.
> > 
> > Second point, the indentation, Xenomai follows the linux kernel
> > rules where the indentation "unit" is a tab characters which should
> > be displayed as 8 spaces by diff. Here your indentation seems to be
> > one space (maybe your mailer did that ?).
> 
> To exclude that option is why I attached the file. For reference, umutilated originals are here: https://github.com/mhaberler/xenomai-2.6/commits/bbcan

The problem is that a patch review usually includes quotes of the
original patches. Writing a reply to your mail by quoting these
patches from an http server or an attachment is way more painful
than simply replying to a mail which contains the patches, inline,
because then the mail client quotes the whole patch and you simply
have to keep what you do not like and write comments below. Note
that I am not writing anything new or original here, this topic is
well covered in the kernel documentation, including ways to
configure various mail clients so that they quote the patches and do
not mangle them. A simple way is to use git send-email.

> 
> I didnt write this - I am just moderating the process, but I can reformat as requested.

Yes, please remove the rename commit, and post the patches with git
send-email. I am sorry to insist, but this is a big patch.

-- 
					    Gilles.


  reply	other threads:[~2015-04-29  4:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-28 15:47 [Xenomai] RT-CAN driver for C_CAN,D_CAN cores ready Michael Haberler
2015-04-28 16:02 ` Gilles Chanteperdrix
2015-04-28 20:19   ` Michael Haberler
2015-04-29  4:30     ` Gilles Chanteperdrix [this message]
2015-04-29  7:05 ` Wolfgang Grandegger
  -- strict thread matches above, loose matches on Subject: below --
2015-04-19 23:01 Michael Haberler
2015-04-26 20:46 ` Wolfgang Grandegger
2015-04-28 14:01   ` Michael Haberler
2015-04-28 14:11     ` Gilles Chanteperdrix
2015-04-29  6:35       ` Wolfgang Grandegger

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=20150429043026.GI1993@hermes.click-hack.org \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=haberlerm@gmail.com \
    --cc=xenomai@xenomai.org \
    /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.