From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 5/5] ARM: mvebu: changes for v3.8
Date: Mon, 26 Nov 2012 10:28:26 +0000 [thread overview]
Message-ID: <201211261028.26334.arnd@arndb.de> (raw)
In-Reply-To: <20121126102805.5337f7f5@skate>
On Monday 26 November 2012, Thomas Petazzoni wrote:
> Right. The problem is that some of the last developments had many
> dependencies against the previous developments, from various branches.
> So I wasn't sure how to do this last developments, and I did merge the
> branches containing the previous developments that I needed.
>
> I am really open to suggestions on how to improve my Git workflow to
> handle this better. It certainly wasn't my intention to have this
> "test-the-merge" thing appear publicly.
>
One thing that Sascha Hauer first introduced was an extra branch that
has everything merged together to show how you want to handle
the conflicts. We'll then merge the individual branches and in the
end can check if there is any difference to what you had.
Arnd
next prev parent reply other threads:[~2012-11-26 10:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-24 5:11 [GIT PULL 1/5] ARM: orion: fixes for v3.8 Jason Cooper
2012-11-24 5:11 ` [GIT PULL 2/5] ARM: orion: cleanup " Jason Cooper
2012-11-24 5:11 ` [GIT PULL 3/5] ARM: orion: boards " Jason Cooper
2012-11-24 5:11 ` [GIT PULL 4/5] ARM: orion: dt " Jason Cooper
2012-11-24 5:11 ` [GIT PULL 5/5] ARM: mvebu: changes " Jason Cooper
2012-11-24 5:17 ` [GIT PULL 1/5] ARM: orion: fixes for *v3.7* Jason Cooper
[not found] ` <50b056f7.8687e50a.170d.7c22SMTPIN_ADDED_MISSING@mx.google.com>
2012-11-26 9:16 ` [GIT PULL 5/5] ARM: mvebu: changes for v3.8 Olof Johansson
2012-11-26 9:28 ` Thomas Petazzoni
2012-11-26 10:28 ` Arnd Bergmann [this message]
2012-11-26 10:35 ` Thomas Petazzoni
2012-11-26 12:24 ` Jason Cooper
2012-11-26 13:06 ` Arnd Bergmann
2012-11-30 17:08 ` Olof Johansson
2012-11-30 7:27 ` Gregory CLEMENT
[not found] ` <50b056f6.c188e50a.1750.ffff84caSMTPIN_ADDED_MISSING@mx.google.com>
2012-11-26 9:17 ` [GIT PULL 4/5] ARM: orion: dt " Olof Johansson
2012-11-26 9:35 ` Olof Johansson
2012-11-26 13:56 ` Jason Cooper
[not found] ` <50b056f7.452ce00a.4217.69b0SMTPIN_ADDED_MISSING@mx.google.com>
2012-11-26 9:19 ` [GIT PULL 3/5] ARM: orion: boards " Olof Johansson
2012-11-26 13:58 ` Jason Cooper
[not found] ` <50b056f6.4689e50a.542a.ffff8136SMTPIN_ADDED_MISSING@mx.google.com>
2012-11-26 9:19 ` [GIT PULL 2/5] ARM: orion: cleanup " Olof Johansson
[not found] <E1Tc82J-0001T0-7f@merlin.infradead.org>
2012-11-27 15:01 ` [GIT PULL 5/5] ARM: mvebu: changes " Gregory CLEMENT
2012-11-27 15:37 ` Jason Cooper
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201211261028.26334.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.