diff options
author | Johannes Schindelin <Johannes.Schindelin@gmx.de> | 2007-05-01 23:42:44 +0200 |
---|---|---|
committer | Shawn O. Pearce <spearce@spearce.org> | 2007-05-02 13:22:34 -0400 |
commit | 775477aa1da94cb9fb9b9afdc217231a0cd42ac1 (patch) | |
tree | b503ff64c120c824e60a30abcdb891b3396d3be3 /Documentation/diffcore.txt | |
parent | GIT v1.5.1.3 (diff) | |
download | tgif-775477aa1da94cb9fb9b9afdc217231a0cd42ac1.tar.xz |
Teach import-tars about GNU tar's @LongLink extension.
This extension allows GNU tar to process file names in excess of the 100
characters defined by the original tar standard. It does this by faking a
file, named '././@LongLink' containing the true file name, and then adding
the file with a truncated name. The idea is that tar without this
extension will write out a file with the long file name, and write the
contents into a file with truncated name.
Unfortunately, GNU tar does a lousy job at times. When truncating results
in a _directory_ name, it will happily use _that_ as a truncated name for
the file.
An example where this actually happens is gcc-4.1.2, where the full path
of the file WeThrowThisExceptionHelper.java truncates _exactly_ before the
basename. So, we have to support that ad-hoc extension.
This bug was noticed by Chris Riddoch on IRC.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
Diffstat (limited to 'Documentation/diffcore.txt')
0 files changed, 0 insertions, 0 deletions