| To: | Greg Banks <gnb@xxxxxxx> |
|---|---|
| Subject: | Re: [patch] fix parallel build failures in xfsprogs-3.0.0 |
| From: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
| Date: | Tue, 3 Mar 2009 10:53:41 -0500 |
| Cc: | Andreas Gruenbacher <agruen@xxxxxxx>, Christoph Hellwig <hch@xxxxxxxxxxxxx>, Mike Frysinger <vapier@xxxxxxxxxx>, Eric Sandeen <sandeen@xxxxxxxxxxx>, xfs-oss <xfs@xxxxxxxxxxx> |
| In-reply-to: | <49A9E555.7040607@xxxxxxx> |
| References: | <200902240010.25434.vapier@xxxxxxxxxx> <200902261817.02604.agruen@xxxxxxx> <49A794D3.2000904@xxxxxxx> <200902271055.51564.agruen@xxxxxxx> <49A9E555.7040607@xxxxxxx> |
| User-agent: | Mutt/1.5.18 (2008-05-17) |
On Sun, Mar 01, 2009 at 12:31:01PM +1100, Greg Banks wrote: > If the point here is to reduce the workload and potential errors > involved in making a release, you could add a release: target to the > Makefile to do the release procedure. That target only needs to work > for the maintainer, so it's relatively easy. You could do the stored > version bump, the tagging, the autotools futzing, and release tarball > building in there. The xfs tools (and acl/attr which use the same buildsystem) have a Makepkgs script that's supposed to do this with some help from the built system. I'm not sure we should add generating the tags and updating doc/CHANGES to it, but everything else is automated iff we actually use it. |
| Previous by Date: | Re: [patch] fix parallel build failures in xfsprogs-3.0.0, Christoph Hellwig |
|---|---|
| Next by Date: | Re: next-20090220: XFS: inconsistent lock state, Eric Sandeen |
| Previous by Thread: | Re: [patch] fix parallel build failures in xfsprogs-3.0.0, Christoph Hellwig |
| Next by Thread: | Re: [patch] fix parallel build failures in xfsprogs-3.0.0, Christoph Hellwig |
| Indexes: | [Date] [Thread] [Top] [All Lists] |