From: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
To: Jim Meyering <jim@meyering.net>
Cc: git@vger.kernel.org
Subject: Re: Set permissions of each new file before "cvs add"ing it.
Date: Mon, 4 Dec 2006 17:51:49 +0100 [thread overview]
Message-ID: <200612041751.49652.robin.rosenberg.lists@dewire.com> (raw)
In-Reply-To: <87ac24zrk0.fsf@rho.meyering.net>
söndag 03 december 2006 20:51 skrev Jim Meyering:
> Without the following patch, git-cvsexportcommit would fail to propagate
> permissions of files added in git to the CVS repository. I.e., when I
> added an executable script in coreutils' git repo, then tried to propagate
> that addition to the mirroring CVS repository, the script ended up added
> not executable there.
The patch to cvsexportcommit I sent a couple of weeks ago fixes the execution
bit, along with most other flaws. Jounio had some objections that I haven't
fixed yet. Hacking the Eclipse plugin was much more fun :)
I added this test case just to verify it on top of my previous patch.
-- robin
diff --git a/t/t9200-git-cvsexportcommit.sh b/t/t9200-git-cvsexportcommit.sh
index 75b9f38..63eafc8 100755
--- a/t/t9200-git-cvsexportcommit.sh
+++ b/t/t9200-git-cvsexportcommit.sh
@@ -195,4 +195,19 @@ test_expect_success \
! git-cvsexportcommit -c $id
)'
+test_expect_success \
+ 'Retain execute bit' \
+ 'mkdir G &&
+ echo executeon >G/on &&
+ chmod +x G/on &&
+ echo executeoff >G/off &&
+ git add G/on &&
+ git add G/off &&
+ git commit -a -m "Execute test" &&
+ (cd "$CVSWORK" &&
+ git-cvsexportcommit -c HEAD
+ test -x G/on &&
+ ! test -x G/off
+ )'
+
prev parent reply other threads:[~2006-12-04 16:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-03 19:51 Set permissions of each new file before "cvs add"ing it Jim Meyering
2006-12-04 2:41 ` Junio C Hamano
2006-12-04 2:47 ` Junio C Hamano
2006-12-04 7:55 ` Jim Meyering
2006-12-04 16:51 ` Robin Rosenberg [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=200612041751.49652.robin.rosenberg.lists@dewire.com \
--to=robin.rosenberg.lists@dewire.com \
--cc=git@vger.kernel.org \
--cc=jim@meyering.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 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 NNTP newsgroup(s).