Bug 732037 - Drift does not detect empty directories
Summary: Drift does not detect empty directories
Status: NEW
Alias: None
Product: RHQ Project
Classification: Other
Component: drift
Version: 4.1
Hardware: Unspecified
OS: Unspecified
medium vote
Target Milestone: ---
: ---
Assignee: RHQ Project Maintainer
QA Contact: Mike Foley
Depends On:
Blocks: 707225
TreeView+ depends on / blocked
Reported: 2011-08-19 14:45 UTC by Mike Foley
Modified: 2011-11-01 19:49 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Last Closed:

Attachments (Terms of Use)

Description Mike Foley 2011-08-19 14:45:12 UTC
Description of problem:  Drift does not detect empty directories

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.  create empty directory in folder being watched by drift
Actual results:
drift does not detect it

Expected results:
Not exactly clear what the expected behavior is...

some discussion around what is expected:
<mazz> jshaughn: mfoley: it is a design decision that folders are not tracked
<jshaughn> far-flung use case
<mazz> only content, bits, files
<mazz> kinda like how git works
<mazz> so empty directories coming and going are not tracked for drift
<mfoley> ok ... 
<jshaughn> so use empty files if you want markers 
<jshaughn> and you want to track using this stuff
<ccrouch> jshaughn: thats not our call
<jshaughn> I don't see how that is drift
<pilhuhn> someone laying down an exploded war file with no content for the start 
<jshaughn> ccrouch: what we're saying is if you want that it will require redesign
<ccrouch> mfoley: i think its a perfectly reasonable question to ask, log it as low priority bug and include this conversation, so when others have the same question they can see the discussion

Comment 1 Jay Shaughnessy 2011-11-01 19:49:42 UTC
Just an update: There has been no support added for this use case. So, it
remains as described above, the coming and going of empty directories are
not tracked as drift.

Note You need to log in before you can comment on or make changes to this bug.