linux-kernel - Re: linux-next: manual merge of the v4l-dvb tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Thu, 13 May 2010 15:59:39 +1000
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Mauro Carvalho Chehab <mchehab@...radead.org>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: linux-next: manual merge of the v4l-dvb tree

Hi Mauro,

On Thu, 13 May 2010 02:18:33 -0300 Mauro Carvalho Chehab <mchehab@...radead.org> wrote:
>
> I'll be pulling from Linus on my tree. I did it yesterday, after my last changes,
> but it seems that I've made a huge mistake... Several conflicts that I've already
> fixed reappeared. I suspect that I've merged it with an older temporary branch
> by mistake.

That explains it.

> Anyway, it is fixed, by simply going back to the last reflog before the error,
> and re-merging the new patches again. A pull from Linus didn't show any conflict.
> 
> So, it should be now OK for you to merge.

Excellent, thanks.

> > Please consider changing your work flow so that you don't rebase things
> > in your tree before sending them to Linus.
> 
> I'm already in process of changing my procedure. The problem is that I didn't find
> yet a perfect way to handle my tree. I'm getting some new ideas, and intend to implement
> them for 2.6.35 development cycle (linux-next for 2.6.36).

OK, good.  The process doesn't have to be perfect ... ;-)

-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au
http://www.canb.auug.org.au/~sfr/

Content of type "application/pgp-signature" skipped