All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joel Becker <jlbec@evilplan.org>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH] Remove versioning information
Date: Tue, 3 Dec 2013 07:38:52 +0000	[thread overview]
Message-ID: <20131203073852.GB7047@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20131203000635.GC16774@wotan.suse.de>

On Mon, Dec 02, 2013 at 04:06:35PM -0800, Mark Fasheh wrote:
> On Tue, Nov 26, 2013 at 05:37:27PM -0600, Goldwyn Rodrigues wrote:
> > The versioning information is confusing for end-users. The numbers
> > are stuck at 1.5.0 while the tools version have moved to 1.8.2.
> > 
> > I suggest removing the versioning system in the ocfs2 module and let
> > the kernel version be the guide to debug issues. However, if
> > you think versioning is still required, please state the reason and
> > modify the version string in the *ver.h files.
> 
> Thanks for this. Once upon a time the versioning helped us but these days
> it's just outdated info
> 
> I would keep the module description if you don't mind. Something short and
> straight forward:
> 
> MODULE_DESCRIPTION("Ocfs2 cluster file system");
> 
> I don't know that we really need a description for the other two modules.

I also agree we should remove the versions.  However, we should retain
descriptions for all of them.

Joel

> 	--Mark
> 
> --
> Mark Fasheh
> 
> _______________________________________________
> Ocfs2-devel mailing list
> Ocfs2-devel at oss.oracle.com
> https://oss.oracle.com/mailman/listinfo/ocfs2-devel

-- 

  reply	other threads:[~2013-12-03  7:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-26 23:37 [Ocfs2-devel] [PATCH] Remove versioning information Goldwyn Rodrigues
2013-11-27  0:26 ` Sunil Mushran
2013-11-28  9:17 ` Lars Marowsky-Bree
2013-12-03  0:06 ` Mark Fasheh
2013-12-03  7:38   ` Joel Becker [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-11-26 19:28 Goldwyn Rodrigues
2013-11-26 22:40 ` Sunil Mushran
2013-11-26 23:33   ` Goldwyn Rodrigues

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=20131203073852.GB7047@ZenIV.linux.org.uk \
    --to=jlbec@evilplan.org \
    --cc=ocfs2-devel@oss.oracle.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.