On Tue, Jul 08, 2014 at 11:40:35AM +0100, Justin Clift wrote:
On 08/07/2014, at 9:53 AM, Anders Blomdell wrote:
snip
2. What are the rules for marking a bug as blocking the trackers (can't
find one for
3.6.0 yet, so currently a moot point).
We should probably create an alias thing
On 2014-07-09 15:02, Niels de Vos wrote:
On Tue, Jul 08, 2014 at 11:40:35AM +0100, Justin Clift wrote:
On 08/07/2014, at 9:53 AM, Anders Blomdell wrote:
snip
2. What are the rules for marking a bug as blocking the trackers (can't
find one for
3.6.0 yet, so currently a moot point).
We
On 07/09/2014 09:56 PM, Anders Blomdell wrote:
BTW: doc/hacker-guide/en-US/markdown/unittest.md seems to lack info on how
to write tests/bugs/bug-*.t files.
unittest.md is for writing code unit tests using cmockery.
some details about writing tests/bugs/bug-*.t files is available at [1].
On 2014-07-07 21:13, Niels de Vos wrote:
On Mon, Jul 07, 2014 at 07:29:15PM +0200, Anders Blomdell wrote:
On 2014-07-07 18:17, Niels de Vos wrote:
On Mon, Jul 07, 2014 at 04:48:18PM +0200, Anders Blomdell wrote:
On 2014-07-07 15:08, Lalatendu Mohanty wrote:
# rpm -U
On 08/07/2014, at 9:53 AM, Anders Blomdell wrote:
snip
2. What are the rules for marking a bug as blocking the trackers (can't find
one for
3.6.0 yet, so currently a moot point).
We should probably create an alias thing for 3.6.0, like we
have for 3.5.2:
On 2014-07-07 18:17, Niels de Vos wrote:
On Mon, Jul 07, 2014 at 04:48:18PM +0200, Anders Blomdell wrote:
On 2014-07-07 15:08, Lalatendu Mohanty wrote:
# rpm -U ./glusterfs-server-3.5qa2-0.722.git2c5eb5c.fc20.x86_64.rpm
./glusterfs-fuse-3.5qa2-0.722.git2c5eb5c.fc20.x86_64.rpm
On Mon, Jul 07, 2014 at 07:29:15PM +0200, Anders Blomdell wrote:
On 2014-07-07 18:17, Niels de Vos wrote:
On Mon, Jul 07, 2014 at 04:48:18PM +0200, Anders Blomdell wrote:
On 2014-07-07 15:08, Lalatendu Mohanty wrote:
# rpm -U ./glusterfs-server-3.5qa2-0.722.git2c5eb5c.fc20.x86_64.rpm
