All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Derrick Stolee <stolee@gmail.com>
Cc: Elijah Newren <newren@gmail.com>,
	Elijah Newren via GitGitGadget <gitgitgadget@gmail.com>,
	Git Mailing List <git@vger.kernel.org>,
	Shaun Case <warmsocks@gmail.com>
Subject: Re: [PATCH] sparse-checkout: avoid staging deletions of all files
Date: Thu, 04 Jun 2020 10:08:57 -0700	[thread overview]
Message-ID: <xmqqzh9ipxli.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <6e5970f6-9b9b-19ba-1035-f4f53d9ac030@gmail.com> (Derrick Stolee's message of "Thu, 4 Jun 2020 11:23:26 -0400")

Derrick Stolee <stolee@gmail.com> writes:

> So maybe be purposeful and include the -a option and expect only the
> .git dir (along with . and ..)?
>
> Something like:
>
> 	cat >expect <<-\EOF &&
> 	.
> 	..
> 	.git
> 	EOF
> 	ls -a clone_no_checkout >actual &&
> 	test_cmp expect actual &&

Is it guaranteed that everybody has dot and dot-dot in their
directory?  

  https://pubs.opengroup.org/onlinepubs/9699919799/utilities/ls.html

has this to describe the "-A" option:

    Write out all directory entries, including those whose names
    begin with a <period> ( '.' ) but excluding the entries dot and
    dot-dot (if they exist).

whose "if they exist" scares me ;-)

  reply	other threads:[~2020-06-04 17:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-04  8:17 [PATCH] sparse-checkout: avoid staging deletions of all files Elijah Newren via GitGitGadget
2020-06-04 14:48 ` Derrick Stolee
2020-06-04 15:05   ` Elijah Newren
2020-06-04 15:23     ` Derrick Stolee
2020-06-04 17:08       ` Junio C Hamano [this message]
2020-06-04 17:18     ` Junio C Hamano
2020-06-04 17:21       ` Junio C Hamano
2020-06-04 16:57 ` Junio C Hamano
2020-06-05  2:41 ` [PATCH v2] " Elijah Newren via GitGitGadget

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=xmqqzh9ipxli.fsf@gitster.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=newren@gmail.com \
    --cc=stolee@gmail.com \
    --cc=warmsocks@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 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.