On Fri, 5 Jul 2013 10:04:37 +1000 Stephen Rothwell
wrote:
>
> On Thu, 4 Jul 2013 19:43:04 +0200 Jan Kara wrote:
> >
> > I'm just writing this to let you know that I had to rebase for_next
> ^^^
> wrong choice of work, you "chose" to rebase.
Hi Jan,
On Thu, 4 Jul 2013 19:43:04 +0200 Jan Kara wrote:
>
> I'm just writing this to let you know that I had to rebase for_next
^^^
wrong choice of work, you "chose" to rebase. :-)
> branch in my linux-fs git tree because I've messed up my
Hello Stephen,
I'm just writing this to let you know that I had to rebase for_next
branch in my linux-fs git tree because I've messed up my tree and for_linus
& for_next branches contained the same patches but with different commit
IDs (fast track fixes). When I pulled for_next into for_linus
Hello Stephen,
I'm just writing this to let you know that I had to rebase for_next
branch in my linux-fs git tree because I've messed up my tree and for_linus
for_next branches contained the same patches but with different commit
IDs (fast track fixes). When I pulled for_next into for_linus
Hi Jan,
On Thu, 4 Jul 2013 19:43:04 +0200 Jan Kara j...@suse.cz wrote:
I'm just writing this to let you know that I had to rebase for_next
^^^
wrong choice of work, you chose to rebase. :-)
branch in my linux-fs git tree because I've messed
On Fri, 5 Jul 2013 10:04:37 +1000 Stephen Rothwell s...@canb.auug.org.au
wrote:
On Thu, 4 Jul 2013 19:43:04 +0200 Jan Kara j...@suse.cz wrote:
I'm just writing this to let you know that I had to rebase for_next
^^^
wrong choice of work,
6 matches
Mail list logo