The Linux Kernel Mailing List
 help / color / mirror / Atom feed
* Rebased for_next branch in my linux-fs git tree
@ 2013-07-04 17:43 Jan Kara
  2013-07-05  0:04 ` Stephen Rothwell
  0 siblings, 1 reply; 3+ messages in thread
From: Jan Kara @ 2013-07-04 17:43 UTC (permalink / raw)
  To: Stephen Rothwell; +Cc: LKML

  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 branch,
the changelog had commit logs for those patches twice which was rather
confusing. The only solution I found was to rebase for_next on top of
for_linus to get rid of the duplicate patches. If there's a cleaner
solution of the situation, I'm happy to learn it for future...

This is just that you know what's going on when you are doing your merge
window statistics :).

								Honza
-- 
Jan Kara <jack@suse.cz>
SUSE Labs, CR

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2013-07-05  2:58 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-07-04 17:43 Rebased for_next branch in my linux-fs git tree Jan Kara
2013-07-05  0:04 ` Stephen Rothwell
2013-07-05  2:57   ` Stephen Rothwell

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox