From: Dave Chinner <david@fromorbit.com>
To: Mika Eloranta <mika.eloranta@ohmu.fi>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] mkfs.xfs: add [-U uuid] option
Date: Tue, 22 Sep 2015 18:25:09 +1000 [thread overview]
Message-ID: <20150922082509.GD3902@dastard> (raw)
In-Reply-To: <AF226911-F11E-42E8-91F1-10C0E2E31E1D@ohmu.fi>
On Tue, Sep 22, 2015 at 11:06:35AM +0300, Mika Eloranta wrote:
> > On 22 Sep 2015, at 10:52, Dave Chinner <david@fromorbit.com> wrote:
> > Don't get me wrong here - I will take an updated patch from you for
> > this functionality. Both you and Eric have very good points as to
> > why mkfs should allow this, but I need to make sure /I/ understand
> > the bigger picture before committing it…
>
> Lesson learned. Coming from my problem domain the feature seemed
> obvious, but I can see the need for being more verbose about the “why?”
> part. I did not realize this feature is not so commonly used.
The usual problem - we're all subject matter experts in
our own domains, and what is obvious to us isn't obvious to
someone in a slightly different domain, even though they interact at
some level.
> Regarding updating the patch: “-U uuid” (mkfs.ext*/mkfs.btrfs -style) or
> "-m uuid=<uuid>” as per proposal by Carlos?
-m uuid=<uuid>, please.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-09-22 8:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-21 17:04 [PATCH] mkfs.xfs: add [-U uuid] option Mika Eloranta
2015-09-21 22:18 ` Dave Chinner
2015-09-21 22:56 ` Mika Eloranta
2015-09-21 23:36 ` Dave Chinner
2015-09-22 6:43 ` Mika Eloranta
2015-09-22 7:22 ` Carlos Maiolino
2015-09-22 7:52 ` Dave Chinner
2015-09-22 8:06 ` Mika Eloranta
2015-09-22 8:25 ` Dave Chinner [this message]
2015-09-22 1:42 ` Eric Sandeen
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=20150922082509.GD3902@dastard \
--to=david@fromorbit.com \
--cc=mika.eloranta@ohmu.fi \
--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