From: Junio C Hamano <gitster@pobox.com>
To: Max Horn <max@quendi.de>
Cc: git@vger.kernel.org, Felipe Contreras <felipe.contreras@gmail.com>
Subject: Re: [PATCH] remote-hg: fix handling of file perms when pushing
Date: Tue, 15 Jan 2013 15:51:53 -0800 [thread overview]
Message-ID: <7vfw220zty.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <1E49829A-0675-40D2-97C6-FD62982A0923@quendi.de> (Max Horn's message of "Tue, 15 Jan 2013 14:06:57 +0100")
Max Horn <max@quendi.de> writes:
> On 15.01.2013, at 14:02, Max Horn wrote:
>
>> Previously, when changing and committing an executable file, the file
>> would loose its executable bit on the hg side. Likewise, symlinks ended
>> up as "normal" files". This was not immediately apparent on the git side
>> unless one did a fresh clone.
>
> Sorry, forgot to sign off, please add:
>
> Signed-off-by: Max Horn <max@quendi.de>
>
> Max
Thanks; merged together with the other patch from Felipe to 'next'.
Unfortunately I noticed the "loose" typo (I think you meant "lose")
after I pushed out the results X-<.
prev parent reply other threads:[~2013-01-15 23:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-15 13:02 [PATCH] remote-hg: fix handling of file perms when pushing Max Horn
2013-01-15 13:06 ` Max Horn
2013-01-15 23:51 ` Junio C Hamano [this message]
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=7vfw220zty.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=max@quendi.de \
/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