public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: Felix Blyakher <felixb@sgi.com>
Cc: Christoph Hellwig <hch@infradead.org>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: xfsprogs/xfsdump release process
Date: Mon, 23 Feb 2009 11:25:43 -0500	[thread overview]
Message-ID: <200902231125.44076.vapier@gentoo.org> (raw)
In-Reply-To: <DCA2D97E-F9A4-4A9E-BC39-CFFF1D0AD2CD@sgi.com>


[-- Attachment #1.1: Type: text/plain, Size: 1190 bytes --]

On Monday 23 February 2009 11:10:44 Felix Blyakher wrote:
> On Feb 23, 2009, at 1:22 AM, Christoph Hellwig wrote:
> > On Sun, Feb 22, 2009 at 11:00:45PM -0600, Felix Blyakher wrote:
> >> Mike, you're absolutely right here. The config files got into the
> >> dmapi tarball by mistake, sorry for this. I verified that neither
> >> xfsprogs nor xfsdump have any extra files. New (clean) dmapi tarball
> >> will be on the oss site shortly.
> >
> > Please don't overwrite already uploaded tarballs.  Let's make a 2.2.10
> > release instead.  We might just use the Makepkgs script for it after
> > fixing it.  See the question and patch on the list for xfsprogs for
> > that, haven't checked dmapi works right yet.
>
> Didn't think that removing the unneeded files from the package
> justifies the version bump. It doesn't change anything for people
> who already downloaded unclean dmapi tarballs.
> Though, if opinion on this matter is that strong, I'd definitely
> bump the version, and will use updated Makepkgs.

the problem is for people (like Gentoo) who already fetched the tarball, 
hashed it, and posted the resulting URL/hash to their packaging systems ...
-mike

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

[-- Attachment #2: Type: text/plain, Size: 121 bytes --]

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

  reply	other threads:[~2009-02-23 16:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-22 18:48 dmapi-2.2.9 release Mike Frysinger
2009-02-22 20:39 ` xfsprogs/xfsdump release process Mike Frysinger
2009-02-23  5:00   ` Felix Blyakher
2009-02-23  7:22     ` Christoph Hellwig
2009-02-23 16:10       ` Felix Blyakher
2009-02-23 16:25         ` Mike Frysinger [this message]
2009-02-23 16:38           ` Felix Blyakher
2009-02-23 19:29             ` Eric Sandeen
2009-02-24 13:20               ` Christoph Hellwig
2009-02-24 15:05   ` Mike Frysinger
2009-02-24 18:44     ` Christoph Hellwig
2009-02-24 19:06       ` Mike Frysinger

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=200902231125.44076.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=felixb@sgi.com \
    --cc=hch@infradead.org \
    --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