From: Andreas Ericsson <ae@op5.se>
To: git@vger.kernel.org
Subject: Re: [PATCH] specfile cleanups
Date: Fri, 11 Nov 2005 12:31:16 +0100 [thread overview]
Message-ID: <43748104.5020707@op5.se> (raw)
In-Reply-To: <7vveyzpmi7.fsf@assigned-by-dhcp.cox.net>
[-- Attachment #1: Type: text/plain, Size: 603 bytes --]
Junio C Hamano wrote:
> Chris Wright <chrisw@osdl.org> writes:
>
>
>>Some specfile cleanups after the split.
>
>
> Thanks.
>
> Does it matter some Requires use comma and others don't?
>
Other than for consistency reasons, no. Most distributions have it in
their conventions to use commas. Some don't.
Most also have the conventions enforced by the attached script as it
enhances readability by removing much un-necessary clutter.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
[-- Attachment #2: specwash.sh --]
[-- Type: application/x-shellscript, Size: 1044 bytes --]
prev parent reply other threads:[~2005-11-11 11:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-11 9:10 [PATCH] specfile cleanups Chris Wright
2005-11-11 9:22 ` Junio C Hamano
2005-11-11 11:31 ` Andreas Ericsson [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=43748104.5020707@op5.se \
--to=ae@op5.se \
--cc=git@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).