Thanks, Hugo.
At this point I mostly want to learn and stay up-to-date with new
patches coming in.
Alex.
On Tue, Jun 26, 2012 at 12:58 PM, Hugo Mills wrote:
> On Tue, Jun 26, 2012 at 11:58:41AM +0300, Alex Lyakas wrote:
>> Hi Hugo,
>> forgive me, but I am somewhat confused.
>> What is the "mai
On Tue, Jun 26, 2012 at 11:58:41AM +0300, Alex Lyakas wrote:
> Hi Hugo,
> forgive me, but I am somewhat confused.
> What is the "main" repo of btrfs-progs, if there is such thing?
> I see patches coming in, but no updates to
> git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-progs.git,
> w
Hi Hugo,
forgive me, but I am somewhat confused.
What is the "main" repo of btrfs-progs, if there is such thing?
I see patches coming in, but no updates to
git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-progs.git,
which I thought was the one.
Can you pls clarify where should I pull upda
On Tue, Jun 5, 2012 at 3:09 PM, Hugo Mills wrote:
>
> I've just pushed out a new integration branch to my git repo. This
> is purely bugfix patches -- there are no new features in this issue of
> the integration branch. I've got a stack of about a dozen more patches
> with new features in them s
Hallo, Hugo,
Du meintest am 06.06.12:
>>>The branch is fetchable with git from:
>>
>>> http://git.darksatanic.net/repo/btrfs-progs-unstable.git/
>>> integration-20120605
>> gcc convert.o -o convert
>> convert.o: In function `btrfs_item_key':
>> /tmp/btrfs-progs-unstable/ctree.h:1404: und
On Wed, Jun 06, 2012 at 06:18:00PM +0200, Helmut Hullen wrote:
> Hallo, Hugo,
>
> Du meintest am 06.06.12:
>
> >> git checkout integration-20120605
>
> [...]
> >Can you compare your Makefile with the one at [1] -- in particular
> > the progs variable at line 21-23, the "all" target on line 3
Hallo, Hugo,
Du meintest am 06.06.12:
>> git checkout integration-20120605
[...]
>Can you compare your Makefile with the one at [1] -- in particular
> the progs variable at line 21-23, the "all" target on line 37, and
> the "btrfs-convert" target on line 97. There definitely should not be
>
On Wed, Jun 06, 2012 at 05:52:00PM +0200, Helmut Hullen wrote:
> Hallo, Hugo,
>
> Du meintest am 06.06.12:
>
> >>> However, the third line with the problem looks like something out
> >>> of date. Possibly a mis-merge?
> >>
> >> Where should I search?
>
> >Well, the first thing would be to tr
Hallo, Hugo,
Du meintest am 06.06.12:
>>> However, the third line with the problem looks like something out
>>> of date. Possibly a mis-merge?
>>
>> Where should I search?
>Well, the first thing would be to try a completely new clone of
> the repo, then git co integration-20120605, and run m
On Wed, Jun 06, 2012 at 05:03:00PM +0200, Helmut Hullen wrote:
> Hallo, Hugo,
>
> Du meintest am 06.06.12:
>
> > However, the third line with the problem looks like something out of
> > date. Possibly a mis-merge?
>
> Where should I search?
Well, the first thing would be to try a completely
Hallo, Hugo,
Du meintest am 06.06.12:
> However, the third line with the problem looks like something out of
> date. Possibly a mis-merge?
Where should I search?
Viele Gruesse!
Helmut
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...
On Wed, Jun 06, 2012 at 01:48:00PM +0200, Helmut Hullen wrote:
> Hallo, Hugo,
>
> Du meintest am 05.06.12:
>
> >The branch is fetchable with git from:
>
> > http://git.darksatanic.net/repo/btrfs-progs-unstable.git/
> > integration-20120605
>
> There seems to be a bug inside:
>
> [...]
>
>
Hallo, Hugo,
Du meintest am 05.06.12:
>The branch is fetchable with git from:
> http://git.darksatanic.net/repo/btrfs-progs-unstable.git/
> integration-20120605
There seems to be a bug inside:
[...]
gcc -g -O0 -o btrfsck btrfsck.o ctree.o disk-io.o radix-tree.o extent-
tree.o print-tree.
I've just pushed out a new integration branch to my git repo. This
is purely bugfix patches -- there are no new features in this issue of
the integration branch. I've got a stack of about a dozen more patches
with new features in them still to go. I'll be working on those
tomorrow. As always, th
14 matches
Mail list logo
