All of lore.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: What's in git.git, and announcing GIT 1.4.2-rc4
Date: Thu, 10 Aug 2006 05:34:48 +0200	[thread overview]
Message-ID: <20060810033448.GH8776@1wt.eu> (raw)
In-Reply-To: <7vy7txxts5.fsf@assigned-by-dhcp.cox.net>

Hi Junio,

On Wed, Aug 09, 2006 at 06:29:30PM -0700, Junio C Hamano wrote:
> GIT 1.4.2-rc4
> 
> It's been a week since -rc3, so here it is.  The changes are
> really small fixes and nothing else.  Let's hope I can tag the
> real 1.4.2 this weekend.

I encountered a problem in 1.4.1 and 1.4-git about 2 weeks ago
(I've not tried 1.4.2-rc4 yet). When applying a git patch which
contains a symlink, the symlink created on the filesystem sometimes
has a wrong name with some chars appended to its end, such as if its
name was not zero-terminated. I always encountered this only when
there were several symlinks in the patch, eg: you create a symlink
first, then commit, then change its dest, then commit, then git-format-patch
and try to apply both patches (git-am -k -3) to another tree. Generally,
the second link will be broken. The index will be OK however, since git-status
will complain about it.

I've tried to find the reason for this problem in the code, but
failed to do so. I remember that the function which calls symlink()
(I don't remember its name, sorry) already gets an invalid name in
path->name or something like this.

That's all I could do because I was really too short in time, and I'm
sorry I really don't have enough time to track this further right now.
However, if you have some time to reproduce it and have questions, I'm
willing to respond you.

Thanks, and sorry again for the lack of information,
Willy

  reply	other threads:[~2006-08-10  3:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-10  1:29 What's in git.git, and announcing GIT 1.4.2-rc4 Junio C Hamano
2006-08-10  3:34 ` Willy Tarreau [this message]
2006-08-10  5:05   ` Junio C Hamano
2006-08-10  5:43     ` Junio C Hamano
2006-08-10  5:42       ` Willy Tarreau
2006-08-10  7:47       ` Johannes Schindelin
2006-08-10  7:59         ` Junio C Hamano
2006-08-10  8:05 ` Johannes Schindelin
2006-08-10  8:10   ` Junio C Hamano
2006-08-10  8:19   ` Junio C Hamano
2006-08-10  8:27     ` Johannes Schindelin
2006-08-10 13:34 ` Alex Riesen
2006-08-10 14:00   ` Johannes Schindelin
2006-08-10 14:30     ` Alex Riesen

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=20060810033448.GH8776@1wt.eu \
    --to=w@1wt.eu \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    /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.