git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Riesen <raa.lkml@gmail.com>
To: Mark Desnoyer <mdesnoyer@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Files not deleted when merging after a rename
Date: Thu, 24 Jan 2008 08:52:02 +0100	[thread overview]
Message-ID: <20080124075202.GB3193@steel.home> (raw)
In-Reply-To: <d997e2110801221808r22f19ec9qc1c452e13c7698df@mail.gmail.com>

Mark Desnoyer, Wed, Jan 23, 2008 03:08:21 +0100:
> Definitely not Winblows. I try to avoid it even with a 10ft pole. I'm
> running Ubuntu 7.10.

Anything mounted in?

> Could you define "exclusively tracked files"? I'm not sure what you mean here.

I asked if the directories contained something else besides the files
known to git.

  reply	other threads:[~2008-01-24  7:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-21 19:45 Files not deleted when merging after a rename Mark Desnoyer
2008-01-21 21:20 ` Alex Riesen
2008-01-21 21:45   ` Mark Desnoyer
2008-01-22  7:28     ` Alex Riesen
2008-01-23  2:08       ` Mark Desnoyer
2008-01-24  7:52         ` Alex Riesen [this message]
2008-01-23  8:19       ` Dmitry Potapov
2008-01-24  7:56         ` Alex Riesen

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=20080124075202.GB3193@steel.home \
    --to=raa.lkml@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=mdesnoyer@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).