Project

General

Profile

Actions

Defect #3421

closed

Mercurial reads files from working dir instead of changesets

Added by Luke Hoersten almost 15 years ago. Updated about 13 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Toshi MARUYAMA
Category:
SCM
Target version:
Start date:
2009-05-26
Due date:
% Done:

0%

Estimated time:
Resolution:
Fixed
Affected version:

Description

Currently the Mercurial plugin tries to read the file contents from the working directory (similar to the "staging area" in Git) instead of the changesets themselves. This means when you try to view a file that's been removed from whatever changeset is checked out in the working dir, it will be not found. Or, trying to view a certain version of a file that does exist in the working dir will just display whatever version was checked out. This seems to be undesirable behavior. It'd be nice to use a null working directory similar to Git's "bare" staging area.


Files

redmine-mercurial.patch (3.78 KB) redmine-mercurial.patch Mercurial fix c.o. Ian Cardenas Luke Hoersten, 2009-06-09 15:33
size.py (1.33 KB) size.py Mercurial size extension c.o. Ian Cardenas Luke Hoersten, 2009-12-19 04:20
branch00.png (9.35 KB) branch00.png Toshi MARUYAMA, 2010-03-11 11:30
branch01.png (8.79 KB) branch01.png Toshi MARUYAMA, 2010-03-11 11:30

Related issues

Related to Redmine - Feature #4455: Mercurial overhaulClosedToshi MARUYAMA2009-12-21

Actions
Has duplicate Redmine - Defect #6458: Mercurial View just a directory browserClosed2010-09-21

Actions
Actions

Also available in: Atom PDF