public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Tulak <jtulak@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: sandeen@redhat.com, xfs@oss.sgi.com
Subject: Re: [PATCH v2] xfsprogs: blkid is now mandatory
Date: Tue, 7 Jul 2015 11:10:58 -0400 (EDT)	[thread overview]
Message-ID: <1156743222.24471614.1436281858017.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20150703151904.GA13839@infradead.org>



----- Original Message -----
> From: "Christoph Hellwig" <hch@infradead.org>
> 
> Can you wrap your commit description lines after ~ 75 characters,
> please?
>
Sure. I changed it to ~ 68 by Dave's suggestion.

> 
> > +AC_HAVE_BLKID_TOPO(yes)
> 
> I don't think we'll need an unused argument for AC_HAVE_BLKID_TOPO.

Fixed.

> 
> > -Mac OS X Instructions
> > -=====================
> 
> Why do you remove this section?
> 

I shouldn't put it into this patch but a standalone one: I tried to build the current version of XFS on OS X (10.10 Yosemite), but so far without a success. (I got to some errors in #defines where I thought I have better things to do.) Neither Macports, nor Homebrew [*] seems to ships XFS... Essentially, even if our docs contain a howto for OS X, it is not working and it looks like no one is using it. So I found this section ready for discarding. :-)

Regarding OS X and blkid... Macports contains util-linux with libblkid, so the new dependency shouldn't be breaking the possibility to port it, if anyone wants to try it...

[*] Macports and Hombrew - two biggest (AFAIK the only ones who are widely used) software repositories for OS X in Linux/BSD style. Macports are basically a port of BSD's Port.

> >  
> >  default: depend $(LTCOMMAND)
> >  
> > -ifneq ($(ENABLE_BLKID),yes)
> > -default: $(FSTYP)
> > -endif
> > -
> >  include $(BUILDRULES)
> >  
> > -$(FSTYP):
> > -	@echo "    [CC]     $@"
> > -	$(Q)$(LTLINK) $@.c -o $@ $(CFLAGS) $(LDFLAGS) $(LIBDISK) $(PLDLIBS)
> > -
> 
> 
> Please remove fstyp.c  and the definition of FSTYP in the Makefile as well.
> 

I assume fstyp.h should go too...

Jan

-- 
Jan Tulak
jtulak@redhat.com

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

  parent reply	other threads:[~2015-07-07 15:11 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-01 16:01 [PATCH] xfsprogs: blkid is now mandatory Jan Tulak
2015-07-01 22:55 ` Dave Chinner
2015-07-02 10:27   ` Jan Tulak
2015-07-02 10:43     ` [PATCH v2] " Jan Tulak
2015-07-03 15:19       ` Christoph Hellwig
2015-07-03 23:45         ` Dave Chinner
2015-07-07 15:10         ` Jan Tulak [this message]
2015-07-08  9:14           ` [PATCH v3] " Jan Tulak
2015-07-21 12:39             ` Jan Tulak
2015-07-26 16:25               ` Christoph Hellwig
2015-08-03 10:40                 ` Jan Tulak
2015-08-03 17:20                   ` Eric Sandeen
2015-08-04 15:30                     ` Jan Tulak
2015-08-04 16:24                       ` Eric Sandeen
2015-08-06 13:13                         ` Jan Tulak
2015-08-11 16:40                           ` Jan Tulak
2015-07-26 16:28             ` 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=1156743222.24471614.1436281858017.JavaMail.zimbra@redhat.com \
    --to=jtulak@redhat.com \
    --cc=hch@infradead.org \
    --cc=sandeen@redhat.com \
    --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