From: Marius Storm-Olsen <marius@trolltech.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Steffen Prohaska <prohaska@zib.de>,
dmitry.kakurin@gmail.com, git@vger.kernel.org
Subject: Re: [PATCH 2/2] checkout: fix attribute handling in checkout all
Date: Mon, 13 Aug 2007 08:32:58 +0200 [thread overview]
Message-ID: <46BFFB1A.4070704@trolltech.com> (raw)
In-Reply-To: <7vfy2ogdvl.fsf@assigned-by-dhcp.cox.net>
[-- Attachment #1: Type: text/plain, Size: 1421 bytes --]
Junio C Hamano said the following on 13.08.2007 08:14:
> Ok, let's step back a bit and I'll suggest an alternative
> approach to your 1/2. This would hopefully solve 2/2 without
> any code change your patch 2/2 has.
(..snip..)
> I think this approach is very much in line with how the git
> plumbing works, but you would need to know how the world is
> designed to work in order to appreciate it fully. Let's have a
> few paragraphs to give the readers some background.
(..snip..)
> Currently, the attr_stack code reads only from the work tree
> and work tree alone. We could change it to:
>
> - If the directory on the work tree has .gitattributes, use it
> (this is what the current code does);
>
> - Otherwise if the index has .gitattributes at the
> corresponding path, use that instead.
>
> This essentially treats not having .gitattributes files checked
> out as equivalent to having these files checked out unmodified,
> which is very much in line with how the world is designed to
> work.
ACK! We really need this! :-)
In msysgit.git/etc/.gitattributes we have 'termcap -crlf', to avoid
the termcaps being checked out with Windows EOL, if the user happens
to have 'autocrlf = true'. However, when you checkout the working dir
the first time it still has Windows EOL due to exactly this problem.
The above algorithm would alleviate this issue.
--
.marius
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 187 bytes --]
next prev parent reply other threads:[~2007-08-13 6:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-12 20:34 [PATCH 1/2] attr: fix attribute handling if .gitattributes is involved Steffen Prohaska
2007-08-12 20:34 ` [PATCH 2/2] checkout: fix attribute handling in checkout all Steffen Prohaska
2007-08-12 21:50 ` Junio C Hamano
2007-08-12 22:26 ` Steffen Prohaska
2007-08-13 6:14 ` Junio C Hamano
2007-08-13 6:32 ` Marius Storm-Olsen [this message]
2007-08-13 6:50 ` Steffen Prohaska
2007-08-13 7:15 ` Marius Storm-Olsen
2007-08-13 7:32 ` Steffen Prohaska
2007-08-13 8:39 ` Marius Storm-Olsen
2007-08-13 8:51 ` Steffen Prohaska
2007-08-13 14:35 ` Dmitry Kakurin
2007-08-14 8:40 ` [PATCH 1/2] attr.c: refactoring Junio C Hamano
2007-08-14 8:41 ` [PATCH 2/2] attr.c: read .gitattributes from index as well Junio C Hamano
2007-08-13 6:46 ` [PATCH 2/2] checkout: fix attribute handling in checkout all Steffen Prohaska
2007-08-13 16:14 ` Johannes Schindelin
2007-08-13 7:24 ` David Kastrup
2007-08-13 14:55 ` git-update-ref bug? (was: [PATCH 2/2] checkout: fix attribute handling in checkout all) David Kastrup
2007-08-13 20:12 ` [PATCH 2/2] checkout: fix attribute handling in checkout all Junio C Hamano
2007-08-13 1:51 ` [PATCH 1/2] attr: fix attribute handling if .gitattributes is involved Brian Downing
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=46BFFB1A.4070704@trolltech.com \
--to=marius@trolltech.com \
--cc=dmitry.kakurin@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=prohaska@zib.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).