public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: "Linus Lüssing" <linus.luessing@web.de>
To: Antonio Quartulli <antonio@meshcoding.com>
Cc: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] [PATCHv2 next 03/11] batman-adv: fix multicast kerneldoc
Date: Wed, 19 Mar 2014 10:38:25 +0100	[thread overview]
Message-ID: <20140319093825.GI5208@Linus-Debian> (raw)
In-Reply-To: <53295F85.9000508@meshcoding.com>

On Wed, Mar 19, 2014 at 10:12:37AM +0100, Antonio Quartulli wrote:
> Hi Linus,
> 
> On 19/03/14 10:03, Linus Lüssing wrote:
> > Hi Antonio,
> > 
> > Two things are confusing me, firstly:
> > 
> > On Wed, Mar 19, 2014 at 09:08:44AM +0100, Antonio Quartulli wrote:
> >> The kerneldoc should always use the third person singular in
> >> the long function description.
> >> Moreover it should always try use up to 80 chars per line.
> > 
> > vs.
> > 
> > On Sun, May 12, 2013 at 12:55:25AM +0200, Antonio Quartulli wrote:
> >> For some reason we agreed on not using the third person while describing the
> >> function. For consistency I'd suggest you to do the same your kernel doc.
> 
> I think the situation is a little confusing because there is no clear
> statement anywhere.
> We agreed on not using the third person in the function description, but
> we use it in the function "long" description (the one after the arguments).

I'm not quite sure about that. I specifically asked for
clarification back then and got this reply which clearly
references the longer function description:

On Thu, May 16, 2013 at 09:36:37PM +0200, Antonio Quartulli wrote:
> On Thu, May 16, 2013 at 08:16:40PM +0200, Linus Lüssing wrote:
> > > > +/**
> > > > + * batadv_mcast_mla_tt_update - Updates the own MLAs
> > > > + * @bat_priv: the bat priv with all the soft interface information
> > > > + *
> > > > + * Updates the own multicast listener announcements in the translation
> > > 
> > > For some reason we agreed on not using the third person while describing the
> > > function. For consistency I'd suggest you to do the same your kernel doc.
> > 
> > I don't quite understand what you mean, talking in the first or
> > second person seems strange, like "I update the multicast..." or
> > "You update the multicast...". Do you have an example?
> 
> It should look like:
> "Update the own multicast listener announcements in the translation"

well, but nevermind

> 
> >>
> > 
> > Secondly:
> > 
> > Why do you only change it in multicast.{c,h}, why not changing
> > things everywhere? For instance translation-table.c sometimes uses
> > "Returns", sometimes "Return".
> 
> Because these patches are meant to be squashed with what you already
> sent before I send them to David (this is why I have create dos many
> patches with different Introduced-by clauses and this is also why the
> patches are targeting next). They are not going to be sent ad a
> standalone set of changes.

Okay that makes sense then if things are getting squashed before
submission. And actually, I'd be very happy to return to the
third-person singular again, the first-person version always
sounded a little strange to me :).

What do you and others think about using third-person in the
short description, too?

Cheers, Linus

  reply	other threads:[~2014-03-19  9:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-19  8:08 [B.A.T.M.A.N.] [PATCHv2 next 01/11] batman-adv: remove useless goto Antonio Quartulli
2014-03-19  8:08 ` [B.A.T.M.A.N.] [PATCHv2 next 02/11] batman-adv: don't mess up with the netdev refcounting if not needed Antonio Quartulli
2014-03-19 10:02   ` Linus Lüssing
2014-03-19  8:08 ` [B.A.T.M.A.N.] [PATCHv2 next 03/11] batman-adv: fix multicast kerneldoc Antonio Quartulli
2014-03-19  9:03   ` Linus Lüssing
2014-03-19  9:12     ` Antonio Quartulli
2014-03-19  9:38       ` Linus Lüssing [this message]
2014-03-19  8:08 ` [B.A.T.M.A.N.] [PATCHv2 next 04/11] " Antonio Quartulli
2014-03-19  8:08 ` [B.A.T.M.A.N.] [PATCHv2 next 05/11] " Antonio Quartulli
2014-03-19  8:08 ` [B.A.T.M.A.N.] [PATCHv2 next 06/11] " Antonio Quartulli
2014-03-19  8:08 ` [B.A.T.M.A.N.] [PATCHv2 next 07/11] " Antonio Quartulli
2014-03-19  8:08 ` [B.A.T.M.A.N.] [PATCHv2 next 08/11] batman-adv: adjust copyright disclaimer in multicast files Antonio Quartulli
2014-03-19  8:08 ` [B.A.T.M.A.N.] [PATCHv2 next 09/11] batman-adv: fix code style Antonio Quartulli
2014-03-19  8:08 ` [B.A.T.M.A.N.] [PATCHv2 next 10/11] batman-adv: fix more " Antonio Quartulli
2014-03-19  8:08 ` [B.A.T.M.A.N.] [PATCHv2 next 11/11] " Antonio Quartulli

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=20140319093825.GI5208@Linus-Debian \
    --to=linus.luessing@web.de \
    --cc=antonio@meshcoding.com \
    --cc=b.a.t.m.a.n@lists.open-mesh.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox