From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Source code adjustments together with comments?
Date: Wed, 04 Feb 2015 14:41:36 +0100 [thread overview]
Message-ID: <54D22190.1070607@users.sourceforge.net> (raw)
In-Reply-To: <20150204133340.GA25483@rei.scz.novell.com>
> And the tool should, in my opinion, do what is the most reasonable
> action by default.
I guess that there are some software development challenges for
further considerations.
Which rules do you use for the connection of a specific amount
of comments to statements in other source code places?
Would you like to express any preferences for consistent
software builds?
Regards,
Markus
next prev parent reply other threads:[~2015-02-04 13:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-04 8:39 [Cocci] broken comments handling Cyril Hrubis
2015-02-04 12:38 ` Julia Lawall
2015-02-04 12:59 ` Cyril Hrubis
2015-02-04 13:02 ` Julia Lawall
2015-02-04 13:23 ` [Cocci] Source code adjustments together with comments? SF Markus Elfring
2015-02-04 13:27 ` Julia Lawall
2015-02-04 13:35 ` Cyril Hrubis
2015-02-04 13:38 ` Julia Lawall
2015-02-04 13:50 ` Rasmus Villemoes
2015-02-04 13:53 ` Julia Lawall
2015-02-04 13:33 ` Cyril Hrubis
2015-02-04 13:41 ` SF Markus Elfring [this message]
2015-02-04 14:15 ` Cyril Hrubis
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=54D22190.1070607@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=cocci@systeme.lip6.fr \
/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.