[Gluster-users] Timestamp on replicated files and dirs

[Stephan von Krawczynski]

Hello Liam,

thank you for pointing to git and the short explanation. Please understand
that I, too, try to help you. I am currently in the state of investigating
your project. Generally it looks pretty promising, but you should not let your
project hang in a state where there is no working release available for
download. This seems to be the case currently, because all I did was
downloading your latest release, installing it on a testbed of 4 servers and
look what it does. The release tilts the timestamps, so you cannot use it in
production. It is no sign of a bad project to do releases more often. It only
shows people care. git is no replacement for that, a user cannot judge if a
current git does well or not, he only knows it is a _current_ state.
So if you point people with development background to git, that is ok. But be
prepared that average users know hardly more than download, ./configure; make;
make install
Please don't feel offended, it is really a nice project. Just try to look at
it as john-doe-user once in a while :-)

Thanks
Stephan




On Mon, 8 Jun 2009 12:00:08 -0700
Liam Slusser <lslusser at gmail.com> wrote:

> Stephan,
> 
> You can get the newest Gluster snapshot by using git, you can download it
> here http://git-scm.com/download
> 
> Once you have git do:
> 
> git clone git://git.sv.gnu.org/gluster.git glusterfs
> 
> liam
> 
> On Mon, Jun 8, 2009 at 3:20 AM, Stephan von Krawczynski <skraw at ithnet.com>wrote:
> 
> > Hello Liam,
> >
> > I have no idea where to download the git release (I am really looking for a
> > tgz source archive to download). Nevertheless I found something call
> > glusterfs-2.0.2 in the qa-releases dir and tried that. It sets the
> > file-timestamps correctly, but not the dir-timestamps.
> > Is there some place where one can download a daily or weekly source
> > snapshot?
> >
> > Regards,
> > Stephan
> >
> >
> >
> > On Sat, 6 Jun 2009 10:33:12 -0700
> > Liam Slusser <lslusser at gmail.com> wrote:
> >
> > > This has been already fixed in the newest git released so grab that
> > > version if you need it today.  I believe it is included in version
> > > 2.0.2.
> > >
> > > Liam
> > >
> >
> >
>