All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mohammed Aziz Parande" <parande1@umbc.edu>
To: linux-lvm@redhat.com
Subject: [linux-lvm] A Question About LVM
Date: Thu, 4 Feb 2010 19:14:11 -0500	[thread overview]
Message-ID: <00e101caa5f8$2460da40$6d228ec0$@edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 1395 bytes --]

Hi,

 

I am a graduate student in the Department of Information Systems at the
University of Maryland, Baltimore County (UMBC). I am doing research in the
area of software engineering. I would very much appreciate if you could
answer the following questions of mine:

 

1. I was wondering if LVM has gone under any major restructuring/redesign
initiative in its history. Restructuring/redesign initiative can be defined
as a concerted effort during a time period in which major changes were
applied to the code base to improve software architecture/design while
little or no functional enhancement was made. 

 

2. If the project has gone under such an initiative, then would it be
possible for you to give the dates or revision/release numbers that are
"right before" and "right after" this structuring effort? I would like to
checkout the source code from the repository to compare structural
measurements that belong to "before" and "after" snapshots. Note that the
dates and revision/release numbers should be right before and right after
the initiative because I would like to be able to isolate and observe the
effects of this effort. 

 

Your response will be very helpful in our research. Thank you very much for
your time in advance. I look forward to hearing from you soon.

 

 

Regards,

 

Mohammed Aziz

 

P.S. This research is solely performed for academic purposes.

 

 


[-- Attachment #2: Type: text/html, Size: 4423 bytes --]

             reply	other threads:[~2010-02-05  0:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-05  0:14 Mohammed Aziz Parande [this message]
2010-02-05  0:50 ` [linux-lvm] A Question About LVM Denie Andriessen

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='00e101caa5f8$2460da40$6d228ec0$@edu' \
    --to=parande1@umbc.edu \
    --cc=linux-lvm@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.