From: "Paolo Teti" <paolo.teti@gmail.com>
To: "Nguyen Thai Ngoc Duy" <pclouds@gmail.com>
Cc: "Git Mailing List" <git@vger.kernel.org>
Subject: Re: [MinGW port] Unable to repack on Clearcase dynamic views
Date: Wed, 30 May 2007 17:11:58 +0200 [thread overview]
Message-ID: <34a7ae040705300811o22a7d9e9y1ca6e52c4bf23fcc@mail.gmail.com> (raw)
In-Reply-To: <fcaeb9bf0705300742u22b54c78vccbc037fb553141f@mail.gmail.com>
2007/5/30, Nguyen Thai Ngoc Duy <pclouds@gmail.com>:
> Hi,
>
> On clearcase dynamic views (kind of virtual drives), "mv -f a b" won't
> work if "a" is read-only. Because git-repack.sh removes all write
> permission before moving packs, it fails on clearcase dynamic views.
>
> My approach is rather ugly. Does anyone have a better solution?
I hate clearcase, but honestly I have used it forced by a customer..
The real problem is why you need to do a repack in a CC view, but..
to move a file in a Clearcase view you have to use 'cleartool mv ...'
(or 'cleartool relocate') and not the UNIX mv command...
..and he directory where the element to be moved or renamed resides
must be checked out.
next prev parent reply other threads:[~2007-05-30 15:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-30 14:42 [MinGW port] Unable to repack on Clearcase dynamic views Nguyen Thai Ngoc Duy
2007-05-30 15:11 ` Paolo Teti [this message]
2007-05-30 15:33 ` Nguyen Thai Ngoc Duy
2007-05-30 16:30 ` Paolo Teti
2007-05-30 18:28 ` Robin Rosenberg
2007-05-30 18:44 ` Johannes Schindelin
2007-05-30 19:08 ` Nguyen Thai Ngoc Duy
2007-05-30 19:28 ` Robin Rosenberg
2007-05-30 19:48 ` Nguyen Thai Ngoc Duy
2007-05-31 9:46 ` Paolo Teti
2007-05-31 18:51 ` Robin Rosenberg
2007-06-01 18:11 ` Jan Hudec
2007-05-30 15:28 ` Johannes Sixt
[not found] ` <fcaeb9bf0705300840w221c46c1y742388fc9e61c2fa@mail.gmail.com>
2007-05-30 15:43 ` Fwd: " Nguyen Thai Ngoc Duy
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=34a7ae040705300811o22a7d9e9y1ca6e52c4bf23fcc@mail.gmail.com \
--to=paolo.teti@gmail.com \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.com \
/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).