public inbox for lvm2-cvs@sourceware.org help / color / mirror / Atom feed
From: mbroz@sourceware.org To: lvm-devel@redhat.com, lvm2-cvs@sourceware.org Subject: LVM2/lib/misc util.c Date: Mon, 23 Jul 2007 10:41:00 -0000 [thread overview] Message-ID: <20070723104119.6688.qmail@sourceware.org> (raw) CVSROOT: /cvs/lvm2 Module name: LVM2 Changes by: mbroz@sourceware.org 2007-07-23 10:41:19 Modified files: lib/misc : util.c Log message: Fix compilation warning in util.c. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/lib/misc/util.c.diff?cvsroot=lvm2&r1=1.1&r2=1.2 --- LVM2/lib/misc/util.c 2007/07/20 15:48:39 1.1 +++ LVM2/lib/misc/util.c 2007/07/23 10:41:19 1.2 @@ -16,6 +16,9 @@ * Return the address of the last file name component of NAME. * If NAME ends in a slash, return the empty string. */ + +#include "lib.h" + char *last_path_component(char const *name) { char const *slash = strrchr (name, '/');
reply other threads:[~2007-07-23 10:41 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20070723104119.6688.qmail@sourceware.org \ --to=mbroz@sourceware.org \ --cc=lvm-devel@redhat.com \ --cc=lvm2-cvs@sourceware.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: linkBe 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 read-only IMAP folder(s) and NNTP newsgroup(s).