git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: dormando <dormando@rydia.net>
To: git@vger.kernel.org
Subject: Resurrecting symlink problem
Date: Thu, 22 Jun 2006 16:00:53 -0700	[thread overview]
Message-ID: <449B2125.7020402@rydia.net> (raw)

Hey,

We have an issue with cogito/git and not being able to remove symlinks 
from a central remote repo.

First try: cg-rm symlinks*
Complains that I'm trying to delete directories without the -r option. 
So it's resolving the symlinks to the target directory.

git rm -f symlinks*

works. Symlinks are gone, push to repo, everything's happy.

However:

user A git rm -f's the symlinks, pushes to origin
user B cg-update's, then cg-commit's, cg-push's a one line change in an 
unrelated file.

user A cg-update's, and the symlinks come back.

This happens over and over. They appear to disappear if cg-update does a 
fast forward, but not if it does a merge. Any suggestions on how to 
resolve this issue?

I'm still looking at what exactly is going on when user B does that 
cg-update.

Thanks,
-Dormando

                 reply	other threads:[~2006-06-22 23:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=449B2125.7020402@rydia.net \
    --to=dormando@rydia.net \
    --cc=git@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).