Linux CIFS filesystem development
 help / color / mirror / Atom feed
From: Suresh Jayaraman <sjayaraman-IBi9RG/b67k@public.gmane.org>
To: Jeff Layton <jlayton-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org>
Cc: linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	piastry-7qunaywFIewox3rIn2DAYQ@public.gmane.org,
	jaxbrigs-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Subject: Re: [PATCH] docs: update to project resources in README
Date: Tue, 17 Apr 2012 10:12:15 +0530	[thread overview]
Message-ID: <4F8CF4A7.5070109@suse.com> (raw)
In-Reply-To: <1334600063-27527-1-git-send-email-jlayton-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org>

On 04/16/2012 11:44 PM, Jeff Layton wrote:
> diff --git a/README b/README
> index 619dc3f..befe4b3 100644
> --- a/README
> +++ b/README
> @@ -5,8 +5,8 @@ separate package.
>  
>  0. PROJECT RESOURCES
>  
> -    Home page: http://linux-cifs.samba.org/cifs-utils/
> -    Mailing list: linux-cifs-client-w/Ol4Ecudpl8XjKLYN78aQ@public.gmane.org
> +    Home page: http://http://wiki.samba.org/index.php/LinuxCIFS_utils
> +    Mailing list: linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
>      Maintainer: cifs-utils-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org

The "Maintainer" information seems out of date as well. Could you please
update this as well when you are at it?


Suresh

  parent reply	other threads:[~2012-04-17  4:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-16 18:14 [PATCH] docs: update to project resources in README Jeff Layton
     [not found] ` <1334600063-27527-1-git-send-email-jlayton-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org>
2012-04-16 19:30   ` Jeff Layton
2012-04-17  4:42   ` Suresh Jayaraman [this message]
     [not found]     ` <4F8CF4A7.5070109-IBi9RG/b67k@public.gmane.org>
2012-04-17 11:47       ` Jeff Layton
     [not found]         ` <20120417074710.0620bf9c-4QP7MXygkU+dMjc06nkz3ljfA9RmPOcC@public.gmane.org>
2012-04-17 13:33           ` Suresh Jayaraman

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=4F8CF4A7.5070109@suse.com \
    --to=sjayaraman-ibi9rg/b67k@public.gmane.org \
    --cc=jaxbrigs-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=jlayton-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org \
    --cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=piastry-7qunaywFIewox3rIn2DAYQ@public.gmane.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