git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 04/16] update-index: add --checkout/--no-checkout to update CE_NO_CHECKOUT bit
Date: Sun, 14 Sep 2008 11:50:51 -0700 (PDT)	[thread overview]
Message-ID: <m38wtuo92v.fsf@localhost.localdomain> (raw)
In-Reply-To: <1221397685-27715-5-git-send-email-pclouds@gmail.com>

I will comment only on documentation...

Nguyễn Thái Ngọc Duy <pclouds@gmail.com> writes:

> --- a/Documentation/git-update-index.txt
> +++ b/Documentation/git-update-index.txt
> @@ -15,6 +15,7 @@ SYNOPSIS
>  	     [--cacheinfo <mode> <object> <file>]\*
>  	     [--chmod=(+|-)x]
>  	     [--assume-unchanged | --no-assume-unchanged]
> +	     [--checkout | --no-checkout]
>  	     [--ignore-submodules]
>  	     [--really-refresh] [--unresolve] [--again | -g]
>  	     [--info-only] [--index-info]
> @@ -88,6 +89,17 @@ OPTIONS
>  	sometimes helpful when working with a big project on a
>  	filesystem that has very slow lstat(2) system call
>  	(e.g. cifs).
> +--checkout::
> +--no-checkout::
> +	When these flags are specified, the object name recorded
> +	for the paths are not updated. Instead, these options
> +	set and unset the "no-checkout" bit for the paths. This
> +	bit is used for marking files for narrow checkout. If
> +	a path is marked "no-checkout", then it should not be
> +	checked out unless requested by user or needed for a git
> +	command to function.
> +	See linkgit:git-checkout[1] for more information about
> +	narrow checkout.

Low level (porcelain) access to "no checkout" bit/flag, isn't it?

Nice. One caveat: you refer to git-checkout(1), which I think is
updated to include referenced information only later in the series.
Perhaps add "See linkgit:git-checkout[1]..." part only _after_ the
referenced information is in Documentation/git-checkout.txt

>  +
>  This option can be also used as a coarse file-level mechanism
>  to ignore uncommitted changes in tracked files (akin to what

Ooops. It looks like it is continuation line to _previous_ option,
probably --assume-unchanged, which you have interrupted by mistake.

-- 
Jakub Narebski
Poland
ShadeHawk on #git

      parent reply	other threads:[~2008-09-14 18:52 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-14 13:07 [PATCH 00/16] Narrow/Partial/Sparse checkout Nguyễn Thái Ngọc Duy
2008-09-14 13:07 ` [PATCH 01/16] Extend index to save more flags Nguyễn Thái Ngọc Duy
2008-09-14 13:07   ` [PATCH 02/16] Introduce CE_NO_CHECKOUT bit Nguyễn Thái Ngọc Duy
2008-09-14 13:07     ` [PATCH 03/16] update-index: refactor mark_valid() in preparation for new options Nguyễn Thái Ngọc Duy
2008-09-14 13:07       ` [PATCH 04/16] update-index: add --checkout/--no-checkout to update CE_NO_CHECKOUT bit Nguyễn Thái Ngọc Duy
2008-09-14 13:07         ` [PATCH 05/16] ls-files: add --narrow-checkout option to "will checkout" entries Nguyễn Thái Ngọc Duy
2008-09-14 13:07           ` [PATCH 06/16] Add tests for updating no-checkout entries in index Nguyễn Thái Ngọc Duy
2008-09-14 13:07             ` [PATCH 07/16] Prevent diff machinery from examining worktree outside narrow checkout Nguyễn Thái Ngọc Duy
2008-09-14 13:07               ` [PATCH 08/16] checkout_entry(): CE_NO_CHECKOUT on checked out entries Nguyễn Thái Ngọc Duy
2008-09-14 13:07                 ` [PATCH 09/16] ls-files: apply --deleted on narrow area only Nguyễn Thái Ngọc Duy
2008-09-14 13:07                   ` [PATCH 10/16] grep: skip files that have not been checked out Nguyễn Thái Ngọc Duy
2008-09-14 13:08                     ` [PATCH 11/16] unpack_trees(): add support for narrow checkout Nguyễn Thái Ngọc Duy
2008-09-14 13:08                       ` [PATCH 12/16] narrow spec: put '+' before a spec will change semantic of '*' Nguyễn Thái Ngọc Duy
2008-09-14 13:08                         ` [PATCH 13/16] ls-files: add --narrow-match=spec option for testing narrow matching Nguyễn Thái Ngọc Duy
2008-09-14 13:08                           ` [PATCH 14/16] clone: support narrow checkout with --path option Nguyễn Thái Ngọc Duy
2008-09-14 13:08                             ` [PATCH 15/16] checkout: add new options to support narrow checkout Nguyễn Thái Ngọc Duy
2008-09-14 13:08                               ` [PATCH 16/16] ls-files: add --overlay option Nguyễn Thái Ngọc Duy
2008-09-14 21:10                                 ` Jakub Narebski
2008-09-15 19:35                                 ` Junio C Hamano
2008-09-16 12:00                                   ` Nguyen Thai Ngoc Duy
2008-09-16 17:00                                     ` Junio C Hamano
2008-09-14 21:12                               ` [PATCH 15/16] checkout: add new options to support narrow checkout Jakub Narebski
2008-09-16  9:53                               ` Baz
2008-09-16 10:17                               ` Johannes Sixt
2008-09-16 13:13                                 ` Nguyen Thai Ngoc Duy
2008-09-14 19:01                             ` [PATCH 14/16] clone: support narrow checkout with --path option Jakub Narebski
2008-09-15 20:27                               ` Junio C Hamano
2008-09-14 18:58                           ` [PATCH 13/16] ls-files: add --narrow-match=spec option for testing narrow matching Jakub Narebski
2008-09-15 19:34                       ` [PATCH 11/16] unpack_trees(): add support for narrow checkout Junio C Hamano
2008-09-16 11:45                         ` Nguyen Thai Ngoc Duy
2008-09-14 18:56                     ` [PATCH 10/16] grep: skip files that have not been checked out Jakub Narebski
2008-09-15 19:35                   ` [PATCH 09/16] ls-files: apply --deleted on narrow area only Junio C Hamano
2008-09-14 18:55           ` [PATCH 05/16] ls-files: add --narrow-checkout option to "will checkout" entries Jakub Narebski
2008-09-15 20:20             ` Junio C Hamano
2008-09-14 18:50         ` Jakub Narebski [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=m38wtuo92v.fsf@localhost.localdomain \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=pclouds@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).