Git development
 help / color / mirror / Atom feed
From: "Elijah Newren" <newren@gmail.com>
To: "Git Mailing List" <git@vger.kernel.org>
Subject: [BUG?]: unpack-file behavior for blobs corresponding to symlinks
Date: Fri, 19 Sep 2008 08:31:39 -0600	[thread overview]
Message-ID: <51419b2c0809190731j5a77b8ccmba2feecb9c44cc1c@mail.gmail.com> (raw)

Hi,

unpack-file doesn't create symlinks as I'd expect.  I'm not sure if
this is a bug in unpack-file, or in my expectations.

To reproduce:

$ git init
Initialized empty Git repository in /home/newren/testing/.git/
$ echo bla > bar
$ ln -s bar foo
$ git add bar foo
$ git ls-files -s foo
120000 ba0e162e1c47469e3fe4b393a8bf8c569f302116 0       foo
$ git unpack-file ba0e162e1c47469e3fe4b393a8bf8c569f302116
.merge_file_J1hTaV
$ ls -l foo .merge_file_J1hTaV
lrwxrwxrwx  1 enewren enewren 3 Sep 19 08:22 foo -> bar
-rw-------  1 enewren enewren 3 Sep 19 08:23 .merge_file_J1hTaV
$ echo $(cat .merge_file_J1hTaV)
bar

Why is .merge_file_J1hTaV a regular file instead of a symlink?  Is
there an alternative command I can use that would create a symlink to
bar given the information I have from the git ls-files command (and
which also works for creating normal files and other special file
types)?

Thanks,
Elijah

             reply	other threads:[~2008-09-19 14:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-19 14:31 Elijah Newren [this message]
2008-09-19 14:51 ` [BUG?]: unpack-file behavior for blobs corresponding to symlinks Mikael Magnusson
2008-09-19 14:55   ` Elijah Newren
2008-09-19 15:50     ` Junio C Hamano

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=51419b2c0809190731j5a77b8ccmba2feecb9c44cc1c@mail.gmail.com \
    --to=newren@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox