Message ID | E1SaTSI-0005UV-4B@tytso-glaptop.cam.corp.google.com |
---|---|
State | Accepted, archived |
Headers | show |
On Fri, Jun 1, 2012 at 8:07 AM, Theodore Ts'o <tytso@mit.edu> wrote: > > git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git dev Hmm, this is a regular branch, but you *usually* use a tag, and the format of the pull-request imples that too: > ---------------------------------------------------------------- > Ext4 updates for 3.5 > > The major new feature added in this update is Darrick J. Wong's > metadata checksum feature, which adds crc32 checksums to ext4's > metadata fields. There is also the usual set of cleanups and bug > fixes. > > ---------------------------------------------------------------- Is there perhaps a tag I should pull instead? Linus -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On 12-06-01 11:07 AM, Theodore Ts'o wrote: > Ext4 updates for 3.5 > > The major new feature added in this update is Darrick J. Wong's > metadata checksum feature, which adds crc32 checksums to ext4's > metadata fields. There is also the usual set of cleanups and bug > fixes. That sounds vaguely like an on-disk change that may have issues with systems that regularly switch between older and newer kernel versions. Could you elaborate on it a bit more, thanks! -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Fri, Jun 1, 2012 at 8:44 AM, Linus Torvalds <torvalds@linux-foundation.org> wrote: > > Is there perhaps a tag I should pull instead? Never mind, I see it. It's 'ext4_for_linus'. So here's the odd 'git' trick of the day. Do git ls-remote git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4 | less -S to see all the branches and tags. In there, we see the branch you asked me to pull: 5e44f8c374.. refs/heads/dev and then we can see if perhaps any of the tags have that same commit when peeled. So search for 5e44f8c374, and sure enough: .. 4e4d525149.. refs/tags/ext4_for_linus 5e44f8c374.. refs/tags/ext4_for_linus^{} .. so that 'ext4_for_linus' tag (which obviously has a different SHA1 than the commit it points to) points to the same commit (the "^{}" is just the git SHA1 expression for "commit pointed to by object"). So pulling 'ext4_for_linus' instead of 'dev' will get me the same commits you asked me to pull, with the added tag information that your pull request containes. Now I just wonder why your pull request said 'dev' at all. Linus -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Fri, Jun 01, 2012 at 10:19:33AM -0700, Linus Torvalds wrote: > So pulling 'ext4_for_linus' instead of 'dev' will get me the same > commits you asked me to pull, with the added tag information that your > pull request containes. So I should do "git request-pull origin git://... ext4_for_linus" next time, right? Sorry about that. I thought it had included the reference to tag automatically since the text of the tag showed in the request-pull text. > Now I just wonder why your pull request said 'dev' at all. Because that was the name of the branch head that I used; sorry about that. - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Fri, Jun 01, 2012 at 12:45:27PM -0400, Mark Lord wrote: > On 12-06-01 11:07 AM, Theodore Ts'o wrote: > > Ext4 updates for 3.5 > > > > The major new feature added in this update is Darrick J. Wong's > > metadata checksum feature, which adds crc32 checksums to ext4's > > metadata fields. There is also the usual set of cleanups and bug > > fixes. > > That sounds vaguely like an on-disk change that may have issues > with systems that regularly switch between older and newer kernel versions. > > Could you elaborate on it a bit more, thanks! > It's an on-disk change, but it's gated by a superblock "feature flag". So unless you actually activate the feature, you won't get it. If you do activate the feature, then you won't be able to switch between older and newer kernel versions --- at least not and be able to mount the file system read/write. (We have different feature flags that indicate whether or not the kernel is allowed to mount the file system read/write, read/only, or not at all, if it doesn't know about a bit in the COMPAT, COMPAT_RO, or INCOMPAT feature bitmak.) The e2fsprogs support for this feature is currently only in the (rewinding) proposed update branch, so it's not something that I recommend people use just yet. Even though it's been pretty well tested, there are probably still some bugs we still need to shake out. - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Fri, Jun 1, 2012 at 10:43 AM, Ted Ts'o <tytso@mit.edu> wrote: > > So I should do "git request-pull origin git://... ext4_for_linus" next > time, right? Right. > Sorry about that. I thought it had included the reference to tag > automatically since the text of the tag showed in the request-pull > text. Apparently git request-pull is too damn smart for its own good, and will find the tags even when they aren't mentioned, making you think it made it to me. Bot it doesn't - so then I have to go search for them by hand. Added Junio and git to the cc: if git finds the tag and uses that for the request-pull message text, then it should use the tagname for the pull request line too. Or, alternatively, don't be smart at all, and force users to name the tag explicitly. The current "both smart and dumb" combination seems to be the worst of both world. Linus -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html