From: Matthieu Moy <matthieu.moy@grenoble-inp.fr>
To: William Duclot <william.duclot@ensimag.grenoble-inp.fr>
Cc: git@vger.kernel.org,
simon rabourg <simon.rabourg@ensimag.grenoble-inp.fr>,
matthieu moy <matthieu.moy@grenoble-inp.fr>,
antoine queru <antoine.queru@ensimag.grenoble-inp.fr>,
francois beutin <francois.beutin@ensimag.grenoble-inp.fr>
Subject: Re: [PATCH/RFC] Add userdiff built-in pattern for CSS code
Date: Thu, 19 May 2016 16:45:01 +0200 (CEST) [thread overview]
Message-ID: <840800650.10903639.1463669101272.JavaMail.zimbra@imag.fr> (raw)
In-Reply-To: <20160519100625.7945-1-william.duclot@ensimag.grenoble-inp.fr>
> Subject: [PATCH/RFC] Add userdiff built-in pattern for CSS code
We normally write subject lines as "<subsystem>: <description",
hence that would be:
userdiff: add built-in pattern for CSS
william.duclot@ensimag.grenoble-inp.fr wrote:
> CSS is widely used, motivating it being included as a built-in pattern.
> It must be noted that the word_regex for CSS (i.e. the regex defining what is
> a word in the language) does not consider '.' and '#' characters (in CSS
> selectors) to be part of the word. This behavior is documented by the test
> t/t4018/css-rule.
This text wasn't properly wrapped. Please wrap around 72 columns (M-q on Emacs,
or google "text wrap $youreditor" for others).
Also, saying _what_ your patch does is not the most important question here.
Focus on the _why_ in the commit message.
(We had a real-life off-list discussion about this and I agree that it's a
sensible behavior, but others may disagree)
> Add the info in documentation that CSS is now built-in.
This doesn't add much to the patch (we can already see that from the patch
itself). I'd remove it.
Missing sign-off (yours, and you can add mine to mark the fact that I allow
you to contribute to Git as part of your student project).
> +PATTERNS("css",
> + "^([^,{}]+)((,[^}]*\\{)|([ \t]*\\{))$",
> + /* -- */
> + /* This regex comes from W3C CSS specs. Should theorically also allow ISO
s/theorically/theoretically/
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
next prev parent reply other threads:[~2016-05-19 14:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-19 10:06 [PATCH/RFC] Add userdiff built-in pattern for CSS code William Duclot
2016-05-19 14:45 ` Matthieu Moy [this message]
2016-05-19 17:41 ` Eric Sunshine
2016-05-19 18:10 ` William Duclot
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=840800650.10903639.1463669101272.JavaMail.zimbra@imag.fr \
--to=matthieu.moy@grenoble-inp.fr \
--cc=antoine.queru@ensimag.grenoble-inp.fr \
--cc=francois.beutin@ensimag.grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=simon.rabourg@ensimag.grenoble-inp.fr \
--cc=william.duclot@ensimag.grenoble-inp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).