From: Rene Scharfe <rene.scharfe@lsrfire.ath.cx>
To: Linus Torvalds <torvalds@osdl.org>
Cc: git@vger.kernel.org
Subject: [PATCH 0/5] git-tar-tree: add symlink support
Date: Fri, 6 May 2005 22:55:29 +0200 [thread overview]
Message-ID: <20050506205529.GA19518@lsrfire.ath.cx> (raw)
Since symlinks can be stored inside GIT, git-tar-tree should properly
handle them, too. The first three patches do a bit of cleanup to make
adding symlink support easier. The fourth patch actually dirties the
code, also to make the fifth one easier. :) I just couldn't think of a
better way to split the changes and a combined patch of 4&5 did too much
at once.
If a link target is longer than 100 chars than an extended header is
created. Because of the way git-tar-tree handles extended headers that
means the sum of path and target of a symlink must be less than about
490 chars. This is not a limitation of the archive format, so we can
fix it later.
Rene
reply other threads:[~2005-05-06 20:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20050506205529.GA19518@lsrfire.ath.cx \
--to=rene.scharfe@lsrfire.ath.cx \
--cc=git@vger.kernel.org \
--cc=torvalds@osdl.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