Git development
 help / color / mirror / Atom feed
From: Matthias Urlichs <smurf@smurf.noris.de>
To: git@vger.kernel.org
Subject: git-read-tree -m -u doesn't delete files: ?
Date: Mon, 20 Jun 2005 15:46:26 +0200	[thread overview]
Message-ID: <pan.2005.06.20.13.46.23.833207@smurf.noris.de> (raw)

Documentation/git-read-tree.txt states:

     10 yes   yes   N/A     exists   nothing  remove path from cache

and 

  -u::
    After a successful merge, update the files in the work
    tree with the result of the merge.

... which suggests that the file in question should be deleted.
In fcat, if I have a clean tree A, and I do "git-read-tree -m -u A B",
I'd assume that I should have a clean tree B afterwards.

Would it be safe to add all files for which read_tree.c:merge_cache:fn()
returns zero to a "delete me" list?

-- 
Matthias Urlichs   |   {M:U} IT Design @ m-u-it.de   |  smurf@smurf.noris.de
Disclaimer: The quote was selected randomly. Really. | http://smurf.noris.de
 - -
The greatest productive force is human selfishness.



                 reply	other threads:[~2005-06-20 13:43 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=pan.2005.06.20.13.46.23.833207@smurf.noris.de \
    --to=smurf@smurf.noris.de \
    --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