From: Alex Schuilenburg <alex@schuilenburg.org>
To: Simon Kallweit <simon.kallweit@intefo.ch>
Cc: eCos developers <ecos-devel@ecos.sourceware.org>
Subject: Re: Mercurial repository missing file modes
Date: Tue, 10 Nov 2009 22:50:00 -0000 [thread overview]
Message-ID: <4AF9EE17.9000409@schuilenburg.org> (raw)
In-Reply-To: <4AF958D2.40709@intefo.ch>
Simon Kallweit wrote:
> Hi
>
> I'm in the process of moving all my ecos related repositories to git.
> I created a git repository that tracks the current ecos hg repository.
> This tracking repo is then used as the base for my custom fork. This
> all looks fine, except that it occurred to me that the file modes in
> the hg repository are not correct (executable flag). I'll fix that in
> my tracking repo but this should also be fixed in the hg repository as
> soon as possible.
Thanks for the notification.
I have fixed the permissions where the files have shebangs. Otherwise,
files which clearly are not executable but have the permissions set in
CVS are untouched.
-- Alex
>
>
> Simon
>
prev parent reply other threads:[~2009-11-10 22:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-10 12:12 Simon Kallweit
2009-11-10 22:50 ` Alex Schuilenburg [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=4AF9EE17.9000409@schuilenburg.org \
--to=alex@schuilenburg.org \
--cc=ecos-devel@ecos.sourceware.org \
--cc=simon.kallweit@intefo.ch \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).