linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rich Johnston <rjohnston@sgi.com>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: [ANNOUNCE] xfsprogs for-3.1.12 branch has been updated to 40c65a7
Date: Tue, 28 Jan 2014 09:36:08 -0600	[thread overview]
Message-ID: <52E7CE68.6030207@sgi.com> (raw)
In-Reply-To: <20140128042024.GH2212@dastard>



On 01/27/2014 10:20 PM, Dave Chinner wrote:
> On Mon, Jan 27, 2014 at 12:46:58PM -0600, Rich Johnston wrote:
>> Arkadiusz,
>>
>> Thanks for compiling the list.
>>
>> The for-3.1.12  Branch created from "a547280... 3.1.11 release"
>>
>> If there are others you want committed, please let me know.
>
> What testing have you done on the branch?

Just a quick test.  I wanted to get it out for others who are interested 
in this branch to start testing.

>
>> 40c65a7... xfs_metadump: Make -F (force) optional
>> ec3a1f1... xfs_repair: suggest reboot after dangerous repair
>> 8660952... xfsprogs: suggest "-d" option for repair of RO mount
>> 5a8206c... xfs_repair: correct docs for "-t" units
>> 0d5c444... xfs_fsr: fix SWAPEXT failures under selinux
>> f3d3dae... libxfs: fix root inode handling inconsistencies
>> cf507b6... xfsprogs: remove xfs_check references from fsck.xfs
>> script & manpage
>> 6e2f2d1... xfsprogs: fix resource leak in longform_dir2_rebuild()
>> ecde3f9... xfs_repair: test for bad level in dir2 node
>> d299df7... xfs_repair: avoid segfault if reporting progress early in repair
>> e660c2e... Sent: Friday, October 11, 2013 12:38:11 AM Subject:
>> Bug#725971: xfsprogs: config.guess/config.sub out of date for arm64
>
> Can you fix the subject line of this commit, please?

Sorry I missed that.

I can, but a git rebase --interactive e660c2e^ will change the commit 
ids after it.  Is there another way to do this that does not change the 
commit ids?

Thanks
--Rich
>
> Cheers,
>
> Dave.
>

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

  reply	other threads:[~2014-01-28 15:36 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-20 17:22 xfsprogs 3.1.12 and 3.2.0 releases? Arkadiusz Miśkiewicz
2014-01-20 22:30 ` Dave Chinner
2014-01-20 22:42   ` Arkadiusz Miśkiewicz
2014-01-20 23:02     ` Dave Chinner
2014-01-20 23:08       ` Christoph Hellwig
2014-01-20 23:11         ` Ben Myers
2014-01-21  8:17           ` Arkadiusz Miśkiewicz
2014-01-21 23:41             ` Dave Chinner
2014-01-22 14:38               ` Mark Tinguely
2014-01-22 14:54                 ` Mark Tinguely
2014-01-22 14:48               ` Arkadiusz Miśkiewicz
2014-01-22 23:03                 ` Dave Chinner
2014-01-23 22:37                   ` Rich Johnston
2014-01-21  8:22           ` Christoph Hellwig
2014-01-27 18:46 ` [ANNOUNCE] xfsprogs for-3.1.12 branch has been updated to 40c65a7 Rich Johnston
2014-01-28  4:20   ` Dave Chinner
2014-01-28 15:36     ` Rich Johnston [this message]
2014-01-28 16:54       ` Ben Myers
2014-01-28 20:17       ` Dave Chinner
2014-01-28  4:42   ` Dave Chinner
2014-01-28 15:33     ` Rich Johnston
2014-01-28 20:15       ` Dave Chinner
2014-01-28 17:29     ` Arkadiusz Miśkiewicz
2014-01-30 19:20       ` Rich Johnston
2014-01-30 20:20         ` Eric Sandeen
2014-01-30 20:58           ` Rich Johnston
2014-02-19 19:18   ` Rich Johnston
2014-02-19 21:50     ` Dave Chinner
2014-03-14 15:28       ` Rich Johnston
2014-04-07 18:20 ` xfsprogs 3.1.12 and 3.2.0 releases? Rich Johnston
2014-04-07 23:30   ` Dave Chinner
2014-04-08 12:38     ` 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=52E7CE68.6030207@sgi.com \
    --to=rjohnston@sgi.com \
    --cc=david@fromorbit.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;
as well as URLs for NNTP newsgroup(s).