From: Jakob Pfender <jpfender@elegosoft.com>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>,
torvalds@osdl.org, spearce@spearce.org,
johannes.schindelin@gmx.de, peff@peff.net, nico@fluxnic.net,
pclouds@gmail.com, barkalow@iabervon.org,
chriscool@tuxfamily.org, jrnieder@gmail.com, raa.lkml@gmail.com,
Matthieu.Moy@grenoble-inp.fr,
Johannes Sixt <j.sixt@viscovery.net>
Subject: [PATCH] Documentation/git-update-index.txt: Remove obsolete note
Date: Wed, 30 Mar 2011 15:01:57 +0200 [thread overview]
Message-ID: <4D9329C5.3060809@elegosoft.com> (raw)
8dcf39 (Prevent bogus paths from being added to the index) introduced a
check for files beginning with '.', preventing path names such as
`./file`, `dir/./file` or `dir/../file` from being added. This was
reflected in the man page.
d089eba (setup: sanitize absolute and funny paths in get_pathspec())
removed this check without reflecting the change in the man page.
Signed-off-by: Jakob Pfender <jpfender@elegosoft.com>
---
Documentation/git-update-index.txt | 6 ++----
1 files changed, 2 insertions(+), 4 deletions(-)
diff --git a/Documentation/git-update-index.txt
b/Documentation/git-update-index.txt
index 1ca56c8..f0dcd1f 100644
--- a/Documentation/git-update-index.txt
+++ b/Documentation/git-update-index.txt
@@ -152,10 +152,8 @@ you will need to handle the situation manually.
<file>::
Files to act on.
- Note that files beginning with '.' are discarded. This includes
- `./file` and `dir/./file`. If you don't want this, then use
- cleaner names.
- The same applies to directories ending '/' and paths with '//'
+ Note that directories ending in '/' and paths with '//' are
+ discarded.
Using --refresh
---------------
--
1.7.0.4
next reply other threads:[~2011-03-30 13:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-30 13:01 Jakob Pfender [this message]
2011-03-31 12:15 ` [PATCH] Documentation/git-update-index.txt: Remove obsolete note Nguyen Thai Ngoc Duy
2011-03-31 15:18 ` Jakob Pfender
2011-03-31 21:41 ` Junio C Hamano
2011-04-02 8:52 ` Nguyen Thai Ngoc Duy
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=4D9329C5.3060809@elegosoft.com \
--to=jpfender@elegosoft.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=barkalow@iabervon.org \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j.sixt@viscovery.net \
--cc=johannes.schindelin@gmx.de \
--cc=jrnieder@gmail.com \
--cc=nico@fluxnic.net \
--cc=pclouds@gmail.com \
--cc=peff@peff.net \
--cc=raa.lkml@gmail.com \
--cc=spearce@spearce.org \
--cc=torvalds@osdl.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 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.