From: Sven Verdoolaege <Sven.Verdoolaege@cs.kuleuven.ac.be>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: cvs2git and file permissions
Date: Sun, 19 Jun 2005 00:31:15 +0200 [thread overview]
Message-ID: <20050618223115.GA5505@billie.cs.kuleuven.ac.be> (raw)
In-Reply-To: <Pine.LNX.4.58.0506181421070.2268@ppc970.osdl.org>
On Sat, Jun 18, 2005 at 02:23:48PM -0700, Linus Torvalds wrote:
> On Sat, 18 Jun 2005, Sven Verdoolaege wrote:
> >
> > Let cvs checkout in a temporary directory rather than
> > using the pipe option to avoid loss of mode information.
>
> Hmm.. Why do you use the "-N" flag?
I didn't quite know how to interpret the "as short as possible" in
Use the -d dir option to create a directory called
dir for the working files, instead of using the
module name. Unless you also use -N, the paths
created under dir will be as short as possible.
It would appear you do.
> Wouldn't it be much cleaner to _not_ create all those sub-directories
> under ".git-tmp", and instead do something like
>
> "cvs -q -d %s checkout -d .git-tmp -r%s '%s/%s'" ...
> "mv -f .git-tmp/%s %s\n", dir ? dir+1 : name, name
>
> With that changed (and tested ;), I'll happily take it.
Seems to work.
The rm is still needed though. Without it, cvs can get confused.
skimo
--
git-cvs2git: propagate mode information
Let cvs checkout in a temporary directory rather than
using the pipe option to avoid loss of mode information.
Signed-off-by: Sven Verdoolaege <skimo@liacs.nl>
---
commit 188ea2ee70413147fc1b80fedc3fbee02843e590
tree f122fcf591013aff299a4d072eed47255892d3a1
parent fdf95bf8d4d1182db579bd25fe5e25811084eaa6
author Sven Verdoolaege <skimo@kotnet.org> Sat, 18 Jun 2005 23:55:49 +0200
committer Sven Verdoolaege <skimo@kotnet.org> Sat, 18 Jun 2005 23:55:49 +0200
cvs2git.c | 5 ++++-
1 files changed, 4 insertions(+), 1 deletions(-)
diff --git a/cvs2git.c b/cvs2git.c
--- a/cvs2git.c
+++ b/cvs2git.c
@@ -199,7 +199,10 @@ static void update_file(char *line)
if (dir)
printf("mkdir -p %.*s\n", (int)(dir - name), name);
- printf("cvs -q -d %s checkout -r%s -p '%s/%s' > '%s'\n", cvsroot, version, cvsmodule, name, name);
+ printf("cvs -q -d %s checkout -d .git-tmp -r%s '%s/%s'\n",
+ cvsroot, version, cvsmodule, name);
+ printf("mv -f .git-tmp/%s %s\n", dir ? dir+1 : name, name);
+ printf("rm -rf .git-tmp\n");
printf("git-update-cache --add -- '%s'\n", name);
}
prev parent reply other threads:[~2005-06-18 22:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-18 20:52 cvs2git and file permissions Sven Verdoolaege
2005-06-18 21:23 ` Linus Torvalds
2005-06-18 22:31 ` Sven Verdoolaege [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=20050618223115.GA5505@billie.cs.kuleuven.ac.be \
--to=sven.verdoolaege@cs.kuleuven.ac.be \
--cc=git@vger.kernel.org \
--cc=skimo@liacs.nl \
--cc=torvalds@osdl.org \
/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