public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: xfs@oss.sgi.com
Subject: Re: rfc 1/2: specfile: use rpm macros where possible
Date: Wed, 11 Feb 2009 11:25:47 -0600	[thread overview]
Message-ID: <49930A1B.7010905@sandeen.net> (raw)
In-Reply-To: <alpine.LSU.2.00.0902111802320.25232@fbirervta.pbzchgretzou.qr>

Jan Engelhardt wrote:
> parent d8a0f148be5b5ea67ee84c61201e98d345c14eda (v{3.0.0})
> commit c32f9b41de79a420e0896d2d4321ce74235d26ce
> Author: Jan Engelhardt <jengelh@medozas.de>
> Date:   Wed Feb 11 17:52:53 2009 +0100
> 
> specfile: use rpm macros where possible
> 
> This way less places need to be changes (when a developer decides
> to change it..) after the placeholders have been substituted.
> 
> Signed-off-by: Jan Engelhardt <jengelh@medozas.de>
> ---

Fine by me, though I never use the specfile (who does?)

I figure most distros have their own specfile to accomodate
distro-specific policies, macros, etc.

-Eric

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  parent reply	other threads:[~2009-02-11 17:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-11 17:04 rfc 1/2: specfile: use rpm macros where possible Jan Engelhardt
2009-02-11 17:04 ` rfc 2/2: specfile: remove Distribution tag Jan Engelhardt
2009-02-11 17:25 ` Eric Sandeen [this message]
2009-02-15 17:24 ` rfc 1/2: specfile: use rpm macros where possible Christoph Hellwig
2009-02-19 15:25   ` Jan Engelhardt
2009-02-24 19:07     ` Christoph Hellwig
2009-02-25 10:15       ` xfsdump: specfile: remove Distribution/Packager tag Jan Engelhardt
2009-02-25 10:18         ` dmapi: " Jan Engelhardt
2009-02-26 20:28         ` xfsdump: " Christoph Hellwig

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=49930A1B.7010905@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=jengelh@medozas.de \
    --cc=xfs@oss.sgi.com \
    /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