Hi everybody
Just to be inline with current settings
I did what I had to do to build my initrd files, committed it to my
branch forked off of master v4.3
So master should be untouched and clean
mega@luna:~/leaf/devel/leaf.new/bering-uclibc git add repo/busybox/.config
Hi everybody
Thanks for bearing with me, I convinced git to behave like I wanted
(until now) , e.g. I have a branch called nameif off the tag v4.3 in
maint which is tracking origin/maint (I believe).
mega@luna:~/leaf/devel/leaf.new/bering-uclibc git branch
maint
master
* nameif
HI Erich;
just to be shure you've branched nameif from maint and not master?
Am 03.10.2012 14:16, schrieb Erich Titl:
Hi everybody
Thanks for bearing with me, I convinced git to behave like I wanted
(until now) , e.g. I have a branch called nameif off the tag v4.3 in
maint which is
Le 03/10/2012 13:48, Erich Titl a écrit :
Hi everybody
Just to be inline with current settings
I did what I had to do to build my initrd files, committed it to my
branch forked off of master v4.3
So master should be untouched and clean
[1]mega@luna:~/leaf/devel/leaf.new/bering-uclibc git
Le 03/10/2012 11:02, Erich Titl a écrit :
I looked at your reply to the multiple build environment stuff and don't
see how you handle that without having two trees. It is not really a GIT
problem but a problem of the moving target 'build environment'. Most
developers don't care, as they are
