git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Greaves <david@dgreaves.com>
To: Jan-Benedict Glaw <jbglaw@lug-owl.de>
Cc: Brian Gerst <bgerst@didntduck.org>,
	Matthias Urlichs <smurf@smurf.noris.de>,
	git@vger.kernel.org
Subject: Re: [PATCH Cogito] cg-init breaks if . contains sub-dir
Date: Tue, 10 May 2005 09:42:23 +0100	[thread overview]
Message-ID: <428073EF.4090407@dgreaves.com> (raw)
In-Reply-To: <20050510080445.GB8176@lug-owl.de>

Jan-Benedict Glaw wrote:

>On Tue, 2005-05-10 09:52:27 +0200, Jan-Benedict Glaw <jbglaw@lug-owl.de> wrote:
>  
>
>>On Tue, 2005-05-10 01:17:31 -0400, Brian Gerst <bgerst@didntduck.org> wrote:
>>    
>>
>>>But it can handle symlinks:
>>>
>>>	find * -type f -o -type l -print0 | xargs -0r cg-add
>>>      
>>>
>>This won't work because the explicit OR (-o) lower precedence compared
>>to the implicit AND between "-type l" and "-print0", thus this find
>>command will do print0 IFF the matched entry is a symlink. Use something
>>like this instead:
>>
>>	find * \( -type f -o tyle l \) -print0 | ...
>>    
>>
>
>Btw, this won't find dot files, so using "." as the path list (instead
>of "*") might be wise...
>  
>
This is a good thing - git ignores dot-files. see:
  http://www.dgreaves.com/git/git-update-cache.html
*
<file> *
    Files to act on. Note that files begining 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 *//* 

Cogito should eventually spot and remove these since find * will
obviously find files beginning with a dot in subdirectories.

David

-- 


  parent reply	other threads:[~2005-05-10  8:35 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-09 23:39 [PATCH Cogito] cg-init breaks if . contains sub-dir Brandon Philips
2005-05-10  1:36 ` Morten Welinder
2005-05-10  3:41 ` Matthias Urlichs
2005-05-10  5:17   ` Brian Gerst
2005-05-10  7:52     ` Jan-Benedict Glaw
2005-05-10  8:04       ` Jan-Benedict Glaw
2005-05-10  8:36         ` Matthias Urlichs
2005-05-10  8:56           ` Martin Waitz
2005-05-10  8:56           ` Jan-Benedict Glaw
2005-05-10  9:47             ` David Greaves
2005-05-10  8:42         ` David Greaves [this message]
2005-05-10  9:01         ` Junio C Hamano
2005-05-10  9:32           ` Jan-Benedict Glaw
2005-05-10  9:39             ` Matthias Urlichs
2005-05-10  9:45               ` Jan-Benedict Glaw
2005-05-10  9:58                 ` Matthias Urlichs
2005-05-10 21:31                   ` David Mansfield
2005-05-11  5:25                     ` [PATCH Cogito] match pathnames in exclude handling Matthias Urlichs
2005-05-11 21:30                       ` H. Peter Anvin
2005-05-12  7:54                         ` Matthias Urlichs
2005-05-10 15:14                 ` [PATCH Cogito] cg-init breaks if . contains sub-dir H. Peter Anvin
2005-05-12 18:53       ` Petr Baudis

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=428073EF.4090407@dgreaves.com \
    --to=david@dgreaves.com \
    --cc=bgerst@didntduck.org \
    --cc=git@vger.kernel.org \
    --cc=jbglaw@lug-owl.de \
    --cc=smurf@smurf.noris.de \
    /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).