From: Junio C Hamano <junkio@cox.net>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: git@vger.kernel.org
Subject: Re: git-checkout-index, flag ordering and --prefix kludgy handling
Date: Mon, 17 Oct 2005 15:58:27 -0700 [thread overview]
Message-ID: <7voe5nycmk.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <200510162114.27429.blaisorblade@yahoo.it> (blaisorblade@yahoo.it's message of "Sun, 16 Oct 2005 21:14:26 +0200")
Blaisorblade <blaisorblade@yahoo.it> writes:
> I already knew that git-checkout-cache -a -f is wrong. But I
> didn't know that
>
> git-checkout-index -a --prefix=/home/paolo/Uml/space.mnt/paolo/Linux-2.6.git/
>
> is.
> At least, this should be documented in the man page;...
How about a bit further clarification on top of what is there,
like this?
------------
[PATCH] clarify that '-a' is really special in checkout-index.
Signed-off-by: Junio C Hamano <junkio@cox.net>
---
diff --git a/Documentation/git-checkout-index.txt b/Documentation/git-checkout-index.txt
index 1ba6fb2..838059f 100644
--- a/Documentation/git-checkout-index.txt
+++ b/Documentation/git-checkout-index.txt
@@ -44,13 +44,15 @@ OPTIONS
--::
Do not interpret any more arguments as options.
-Note that the order of the flags matters:
+Note that the order of the flags matters for `-a` flag:
git-checkout-index -a -f file.c
will first check out all files listed in the cache (but not overwrite
any old ones), and then force-checkout `file.c` a second time (ie that
one *will* overwrite any old contents with the same filename).
+In other words, `-a` means "operate as if names of all files were
+given here, with the flags given up to this point."
Also, just doing "git-checkout-index" does nothing. You probably meant
"git-checkout-index -a". And if you want to force it, you want
next prev parent reply other threads:[~2005-10-17 22:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-16 19:14 git-checkout-index, flag ordering and --prefix kludgy handling Blaisorblade
2005-10-17 22:58 ` Junio C Hamano [this message]
2005-10-17 22:58 ` Linus Torvalds
2005-10-18 0:33 ` Junio C Hamano
2005-10-18 1:28 ` Linus Torvalds
2005-10-18 2:27 ` Junio C Hamano
2005-10-18 2:48 ` Linus Torvalds
2005-10-18 5:49 ` Teach "git diff" to handle filenames startign with '-' Linus Torvalds
2005-10-18 5:57 ` Handle "-" at beginning of filenames, part 3 Linus Torvalds
2005-10-18 8:34 ` [PATCH] git-checkout: revert specific paths to either index or a given tree-ish Junio C Hamano
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7voe5nycmk.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=blaisorblade@yahoo.it \
--cc=git@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).