All of lore.kernel.org
 help / color / mirror / Atom feed
From: Toby Corkindale <toby.corkindale@rea-group.com>
To: git@vger.kernel.org
Subject: .git/info/attributes not cloned
Date: Thu, 27 Mar 2008 14:08:30 +1100	[thread overview]
Message-ID: <47EB0FAE.5000102@rea-group.com> (raw)

Hi.
If one creates a .git/info/attributes file in a Git repo, it will not be 
present in cloned repos.
I don't know if this is a bug or not, but it /seems/ wrong behaviour to 
me, and reading from the manual pages.

This shell script demonstrates the issue:

#!/bin/bash
mkdir testgit
cd testgit
mkdir original
cd original
git init --shared
echo -e "# gitattributes(5) file\n*.pm ident" > .git/info/attributes
echo "# \$Ident\$" > example.pm
git add example.pm
git commit -m "initial commit"
cd ..
git clone --bare original copy
if [ -e copy/info/attributes ]; then
     echo "Good, attributes file exists."
else
     echo "Bad! attributes file does not exist in copy."
fi

             reply	other threads:[~2008-03-27  3:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-27  3:08 Toby Corkindale [this message]
2008-03-27  3:33 ` .git/info/attributes not cloned Jeff King
2008-03-27  4:23   ` Toby Corkindale
2008-03-27  4:29     ` Jeff King
2008-03-27  4:48       ` Toby Corkindale
2008-03-27  4:53         ` Jeff King
2008-03-28  5:10           ` [BUG?] git-archive ignores remote .gitattributes (was: .git/info/attributes not cloned) Toby Corkindale
2008-03-28 12:22             ` Johannes Schindelin
2008-03-28 13:02               ` Jakub Narebski
2008-03-28 13:22                 ` Johannes Schindelin
2008-03-31  2:47               ` Jeff King
2008-03-31  3:07                 ` [BUG?] git-archive ignores remote .gitattributes Junio C Hamano
2008-04-10  4:14               ` Toby Corkindale

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=47EB0FAE.5000102@rea-group.com \
    --to=toby.corkindale@rea-group.com \
    --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.
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.