From: Eric Sandeen <sandeen@sandeen.net>
To: Rich Johnston <rjohnston@sgi.com>, xfs@oss.sgi.com
Subject: Re: [PATCH V3] xfsprogs: update version for 3.2.0-alpha2
Date: Thu, 21 Nov 2013 10:27:04 -0600 [thread overview]
Message-ID: <528E3458.6040100@sandeen.net> (raw)
In-Reply-To: <528D84E1.3010500@sgi.com>
On 11/20/13, 9:58 PM, Rich Johnston wrote:
>
>
> On 11/20/2013 09:49 PM, Eric Sandeen wrote:
<snip>
>> Just hit the highlights:
>>
>> * What new features?
>> * What changes in behavior?
>> * What bugs were fixed?
>>
>> you have a lot of leeway, but use your editorial powers to create
>> something useful to a user by distilling this noise into a narrative.
>> And fix spelling as needed. ;)
>>
>> If you'd like me to just write the changelog so we can get it out the
>> door, let me know.
>
> Kinda caught up in other things, go for it. English is not my first language. Many thanks Eric.
Ok, I'll come up w/ something tomorrow. I'll take that bullet for you. ;)
(Dave, unless you feel like putting something together before I wake up)
(And I didn't send this prior to waking up! I'll try to get something together
today)
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-11-21 16:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-18 15:03 [patch 1/1] xfsprogs: update version for 3.2.0-alpha2 rjohnston
2013-11-18 15:11 ` Christoph Hellwig
2013-11-18 15:41 ` Rich Johnston
2013-11-18 22:53 ` Dave Chinner
2013-11-19 17:01 ` [PATCH V2] " rjohnston
2013-11-19 17:21 ` Christoph Hellwig
2013-11-19 17:14 ` [PATCH V3] " rjohnston
2013-11-21 3:49 ` Eric Sandeen
2013-11-21 3:58 ` Rich Johnston
2013-11-21 16:27 ` Eric Sandeen [this message]
2013-11-22 18:37 ` [PATCH V4] " rjohnston
2013-11-22 19:04 ` Rich Johnston
2013-11-22 21:09 ` Eric Sandeen
2013-11-25 14:42 ` Rich Johnston
2013-11-25 14:54 ` Christoph Hellwig
2013-11-25 15:00 ` 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=528E3458.6040100@sandeen.net \
--to=sandeen@sandeen.net \
--cc=rjohnston@sgi.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 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.