public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Benny Halevy <bhalevy@panasas.com>
To: Boaz Harrosh <bharrosh@panasas.com>
Cc: NFS list <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH] SQUASHME: DEVONLY: pnfs: Add -pnfs suffix to EXTRAVERSION
Date: Mon, 14 Jun 2010 20:09:38 -0400	[thread overview]
Message-ID: <4C16C4C2.8060806@panasas.com> (raw)
In-Reply-To: <4C0E0387.8070502@panasas.com>

Merged at pnfs-all-2.6.35-rc3-2010-06-14

Thanks!

Benny

On Jun. 08, 2010, 4:47 -0400, Boaz Harrosh <bharrosh@panasas.com> wrote:
> 
> The official way of adding a tree identifier tag to the Kernel
> version-string is a presence of a localversion-* file next to
> the Makefile. It's content is appended to the Linus supplied
> version-string from Makefile.
> 
> After this patch the output is the same as before xxx-2.6.35-rc2-pnfs
> But is a more comfortable way to manage it.
> 
> (The appended "+" in post 2.6.35-rc Kernels is not resolved with
>  this. But I have sent a patch to Linus to fix this issue)
> 
> Signed-off-by: Boaz Harrosh <bharrosh@panasas.com>
> ---
>  Makefile          |    2 +-
>  localversion-pnfs |    1 +
>  2 files changed, 2 insertions(+), 1 deletions(-)
>  create mode 100644 localversion-pnfs
> 
> diff --git a/Makefile b/Makefile
> index 6ac434c..654c31a 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -1,7 +1,7 @@
>  VERSION = 2
>  PATCHLEVEL = 6
>  SUBLEVEL = 35
> -EXTRAVERSION = -rc2-pnfs
> +EXTRAVERSION = -rc2
>  NAME = Sheep on Meth
>  
>  # *DOCUMENTATION*
> diff --git a/localversion-pnfs b/localversion-pnfs
> new file mode 100644
> index 0000000..7523328
> --- /dev/null
> +++ b/localversion-pnfs
> @@ -0,0 +1 @@
> +-pnfs

      parent reply	other threads:[~2010-06-15  0:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-08  8:47 [PATCH] SQUASHME: DEVONLY: pnfs: Add -pnfs suffix to EXTRAVERSION Boaz Harrosh
2010-06-08 10:28 ` Boaz Harrosh
2010-06-15  0:09 ` Benny Halevy [this message]

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=4C16C4C2.8060806@panasas.com \
    --to=bhalevy@panasas.com \
    --cc=bharrosh@panasas.com \
    --cc=linux-nfs@vger.kernel.org \
    /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