From: Christian Thaeter <ct@pipapo•org>
To: Linus Torvalds <torvalds@osdl•org>
Cc: git@vger•kernel.org
Subject: Re: handling symlinks proposal
Date: Sun, 26 Nov 2006 20:50:01 +0100 [thread overview]
Message-ID: <4569EFE9.6010101@pipapo.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0611261034100.3483@woody.osdl.org>
Linus Torvalds wrote:
>
> On Sun, 26 Nov 2006, Christian Thaeter wrote:
>> Git currently keep symlinks always as symlink, I would like to see some
>> optional functionality when handling symlinks.
>
> I can pretty much guarantee that you really don't want to do this, and
> that you'd be _much_ happier using some explicit wrappers around git to
> handle your special needs, than try to teach the SCM to handle symlinks
> specially.
ok agreed, i'll write some script which one can use on a tree to
sanitize symlinks on given rules and/or be used as a pre-commit check.
That has the pretty same effect for my needs and is more sane like you
outlined.
prev parent reply other threads:[~2006-11-26 19:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-26 16:59 handling symlinks proposal Christian Thaeter
2006-11-26 18:25 ` René Scharfe
2006-11-26 18:46 ` Linus Torvalds
2006-11-26 19:50 ` Christian Thaeter [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=4569EFE9.6010101@pipapo.org \
--to=ct@pipapo$(echo .)org \
--cc=git@vger$(echo .)kernel.org \
--cc=torvalds@osdl$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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