All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Sergio Callegari <sergio.callegari@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: symbolic link management in git-archive
Date: Thu, 27 Mar 2008 09:31:23 -0700	[thread overview]
Message-ID: <7v3aqcb02s.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <loom.20080327T112740-539@post.gmane.org> (Sergio Callegari's message of "Thu, 27 Mar 2008 11:29:28 +0000 (UTC)")

Sergio Callegari <sergio.callegari@gmail.com> writes:

> I guess the answer is "no" or "not yet", but is there a way to tell the zip
> backend of git-archive to follow symbolic links rather than to store them?

I am not sure what you mean.  Are you tracking a symbolic link X that
points at Y in your revision and expecting git-archive to include whatever
happens to be at Y (which may or may not even exist) when you run the
command?

If that is the case, the answer is "no" and "will never happen".  If you
are tracking a symbolic link X that points at Y, the information git
tracks is the fact that there is a symbolic link X that points at Y, and
not what Y happens to look like at a random moment.  Change to Y is not
tracked by git so why should you get different output from git-archive of
the same revision before and after you modify Y which is not part of the
revision to begin with?

If that is not what you are asking, please restate the question.

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

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-27 11:29 symbolic link management in git-archive Sergio Callegari
2008-03-27 11:40 ` Miklos Vajna
2008-03-27 11:44   ` Johannes Schindelin
2008-03-27 12:11     ` Sergio Callegari
2008-03-27 16:31 ` Junio C Hamano [this message]
2008-03-27 18:34   ` Sergio Callegari
2008-03-27 19:05     ` Junio C Hamano
2008-03-27 19:20       ` Sergio Callegari
2008-03-31 20:44     ` René Scharfe
2008-03-31 22:12       ` Sergio Callegari

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=7v3aqcb02s.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=sergio.callegari@gmail.com \
    /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.