All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Colin Watson <cjwatson@ubuntu.com>
Cc: Christoph Hellwig <hch@infradead.org>, 725971@bugs.debian.org
Subject: Bug#725971: xfsprogs: config.guess/config.sub out of date for arm64
Date: Tue, 15 Oct 2013 14:29:30 -0700	[thread overview]
Message-ID: <20131015212930.GA5874@infradead.org> (raw)
In-Reply-To: <20131015212448.GM32337@riva.ucam.org>

On Tue, Oct 15, 2013 at 10:24:48PM +0100, Colin Watson wrote:
> I looked, but there's nothing to send; the xfsprogs repository doesn't
> contain those files.  They're updated by the configure target in
> Makefile, which is run as part of ./release.sh via "make dist".  (Good;
> this should be as automatic as possible.)

Oh, forgot about that.

> IOW, any new upstream release will contain updated files as long as the
> developer who built the release has current libtool etc. installed.  But
> of course this should be fixed to auto-update at build time in the
> Debian packaging anyway, since we want to be able to port to new
> architectures without having to upload lots of new source packages or
> take lots of new upstream releases at the same time; it makes life so
> much easier.

As said, I don't disagree with your patch at all, I was just asking for
an additional patch which turned out not to be nessecary.

Thanks a lot!

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

  reply	other threads:[~2013-10-15 21:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-10 13:38 Bug#725971: xfsprogs: config.guess/config.sub out of date for arm64 Colin Watson
2013-10-10 23:24 ` Fwd: " Nathan Scott
2013-10-10 23:56   ` Nathan Scott
2013-10-18 17:39     ` Rich Johnston
2013-10-10 23:25 ` Nathan Scott
2013-10-15 19:42 ` Christoph Hellwig
2013-10-15 21:24   ` Colin Watson
2013-10-15 21:29     ` Christoph Hellwig [this message]
2013-10-18 17:30 ` Rich Johnston

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=20131015212930.GA5874@infradead.org \
    --to=hch@infradead.org \
    --cc=725971@bugs.debian.org \
    --cc=cjwatson@ubuntu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.