From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] GFS2 -nmw tree
Date: Tue, 10 May 2011 13:47:48 +0100 [thread overview]
Message-ID: <1305031668.2839.12.camel@menhir> (raw)
Hi,
I pushed the patch set tidying up the link counts and merging inode.c
and ops_inode.c this morning. However, since I checked the tree out
again, I spotted that git has done a funny with the resulting files. It
looks like if you do:
git rm a
git mv b a
git commit -a
Then you land up with _both_ of a and b missing. The patch displayed ok
in the web interface, and appeared to show the right outcome, but the
"b" (in this case fs/gfs2/inode.c) was missing from the resulting tree.
So I've just done a quick update splitting the final patch in the series
into two, which has fixed the problem.
Sorry about that, if it has caused any confusion. It is exactly the same
changes, but now split over two patches,
Steve.
next reply other threads:[~2011-05-10 12:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-10 12:47 Steven Whitehouse [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-01-03 10:21 [Cluster-devel] GFS2 -nmw tree Steven Whitehouse
2013-09-17 10:44 Steven Whitehouse
2013-04-09 14:10 Steven Whitehouse
2012-07-26 10:24 Steven Whitehouse
2010-11-30 10:57 Steven Whitehouse
2009-11-05 14:12 Steven Whitehouse
2006-12-08 11:34 Steven Whitehouse
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=1305031668.2839.12.camel@menhir \
--to=swhiteho@redhat.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).