[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-ia64
Subject:    Re: [git pull] ia64 changes
From:       Linus Torvalds <torvalds () linux-foundation ! org>
Date:       2010-10-21 21:33:29
Message-ID: AANLkTikzh6LhAwmNkciU3P+qhopYiZNg7LvHhaHW2z4N () mail ! gmail ! com
[Download RAW message or body]

On Thu, Oct 21, 2010 at 9:00 AM, Luck, Tony <tony.luck@intel.com> wrote:
> 
> Peer with extra suspicion at the octo-merge since this is the first
> time I've used one of these to pull in all my topic branches.  I just
> ran:
> $ git merge release drop_do_IRQ fix_early_irq misc-2.6.37 next-fixes \
> optimize-unwind remove-compat-h stack_trace

Looks fine to me. You don't need to list the branch you're already in,
so the "release" part of that git merge command is superfluous, but
with any reasonably modern git version, git will prune out any
duplicate branches and not list them twice in the list of parents
(once for the branch you were on, and once for you asking to merge
that same branch). So it's actually pretty hard to really screw up an
octopus merge, since git will even refuse anything that doesn't merge
automatically and cleanly.

                         Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[prev in list] [next in list] [prev in thread] [next in thread]