Hi
@KP, like the merge commit in master, your last merge commit (f010890d) is
really strange:
Merge branch 'next' of
ssh://leaf.git.sourceforge.net/gitroot/leaf/bering-uclibc into next
In next we must only see merge from master or topic branches. I don't
understand this merge..
Perhaps
Hi Yves;
Am 26.08.2012 10:40, schrieb Yves Blusseau:
Hi
@KP, like the merge commit in master, your last merge commit (f010890d) is
really strange:
Merge branch 'next' of
ssh://leaf.git.sourceforge.net/gitroot/leaf/bering-uclibc into next
In next we must only see merge from master
26.08.2012 12:20, KP Kirchdoerfer пишет:
Hi Yves;
Am 26.08.2012 10:40, schrieb Yves Blusseau:
Hi
@KP, like the merge commit in master, your last merge commit (f010890d) is
really strange:
Merge branch 'next' of
ssh://leaf.git.sourceforge.net/gitroot/leaf/bering-uclibc into next
Hi Andrew;
Enabling zswap in leaf.cfg does not work.
+ chmod 1777 /var/lock
+ chmod 1777 /tmp
+ [ 10M -ge 0 ]
sh: 10M: bad number
The line in leaf.cfg is
zswap=10M
kp
--
Live Security Virtual Conference
Exclusive
26.08.2012 13:37, KP Kirchdoerfer пишет:
Hi Andrew;
Enabling zswap in leaf.cfg does not work.
+ chmod 1777 /var/lock
+ chmod 1777 /tmp
+ [ 10M -ge 0 ]
sh: 10M: bad number
The line in leaf.cfg is
zswap=10M
kp
Hi.
Yes, I missed suffix support. I fixed this into git.
You can use
Le 26 août 2012 à 12:10, Andrew a écrit :
26.08.2012 12:20, KP Kirchdoerfer пишет:
Hi Yves;
Am 26.08.2012 10:40, schrieb Yves Blusseau:
Hi
@KP, like the merge commit in master, your last merge commit (f010890d) is
really strange:
Merge branch 'next' of
Hi all,
i made this mail because i see a lot of commit in next branches without any
topic branch. It's ok if you keep your topic branches private, but it's bad if
you commit directly in next branch.
The next branch must not be used to fix or add new feature. It's an
experimental branch that
Am 26.08.2012 15:02, schrieb Yves Blusseau:
Le 26 août 2012 à 12:10, Andrew a écrit :
26.08.2012 12:20, KP Kirchdoerfer пишет:
Hi Yves;
Am 26.08.2012 10:40, schrieb Yves Blusseau:
Hi
@KP, like the merge commit in master, your last merge commit (f010890d) is
really strange:
Am 25.08.2012 22:22, schrieb Andrew:
25.08.2012 23:02, KP Kirchdoerfer пишет:
Am 25.08.2012 21:47, schrieb Andrew:
25.08.2012 22:30, KP Kirchdoerfer пишет:
Am 25.08.2012 21:20, schrieb Andrew:
25.08.2012 22:12, KP Kirchdoerfer пишет:
Am 25.08.2012 17:29, schrieb Andrew:
25.08.2012 18:21, KP
26.08.2012 17:24, KP Kirchdoerfer пишет:
Am 26.08.2012 12:46, schrieb Andrew:
26.08.2012 13:37, KP Kirchdoerfer пишет:
Hi Andrew;
Enabling zswap in leaf.cfg does not work.
+ chmod 1777 /var/lock
+ chmod 1777 /tmp
+ [ 10M -ge 0 ]
sh: 10M: bad number
The line in leaf.cfg is
zswap=10M
So good !
Yes i will switch again 2.22. But if all is ok we can merge the commit into
master (with the same parent). So andrew can you commit your topic branch
directly into master (no cherry-pick). You must merge the same topic branch
that you use to commit into next. If your made
Am 26.08.2012 16:33, schrieb Yves Blusseau:
So good !
Yes i will switch again 2.22. But if all is ok we can merge the commit into
master (with the same parent). So andrew can you commit your topic branch
directly into master (no cherry-pick). You must merge the same topic branch
that you
Le 26 août 2012 à 16:47, KP Kirchdoerfer a écrit :
Am 26.08.2012 16:33, schrieb Yves Blusseau:
So good !
Yes i will switch again 2.22. But if all is ok we can merge the commit
into master (with the same parent). So andrew can you commit your topic
branch directly into master (no
Am 26.08.2012 17:01, schrieb Yves Blusseau:
Le 26 août 2012 à 16:47, KP Kirchdoerfer a écrit :
Am 26.08.2012 16:33, schrieb Yves Blusseau:
So good !
Yes i will switch again 2.22. But if all is ok we can merge the commit
into master (with the same parent). So andrew can you commit your
As git cherry -v master give me:
+ 0306cd0 enabled mkswap and swapon/swapoff applets in bb
+ f662339 Disabled patch that removes swap stats (now swap is on by default)
+ 90ff671 fixed upnpd assembly
+ b3ec368 added userland zram support; some init script rework
+ 027d722 removed unneeded delay;
Le 26 août 2012 à 17:24, Yves Blusseau a écrit :
As git cherry -v master give me:
+ 0306cd0 enabled mkswap and swapon/swapoff applets in bb
+ f662339 Disabled patch that removes swap stats (now swap is on by default)
+ 90ff671 fixed upnpd assembly
+ b3ec368 added userland zram support;
Am 26.08.2012 18:32, schrieb Yves Blusseau:
Le 26 août 2012 à 17:24, Yves Blusseau a écrit :
As git cherry -v master give me:
+ 0306cd0 enabled mkswap and swapon/swapoff applets in bb
+ f662339 Disabled patch that removes swap stats (now swap is on by default)
+ 90ff671 fixed upnpd
26.08.2012 19:32, Yves Blusseau пишет:
Le 26 août 2012 à 17:24, Yves Blusseau a écrit :
As git cherry -v master give me:
+ 0306cd0 enabled mkswap and swapon/swapoff applets in bb
+ f662339 Disabled patch that removes swap stats (now swap is on by default)
+ 90ff671 fixed upnpd assembly
+
Hi all,
i have added a new tool: tool/setup-builddir and associate a makefile variable
to it: $(BT_SETUP_BUILDDIR)
This tool help to uncompress source tarball in build directory.
In the buildtool.mk you can rewrite all:
bzcat $(XXX_SOURCE) | tar -xvf -
or
zcat $(XXX_SOURCE) |
19 matches
Mail list logo