From: Markus Heidelberg <markus.heidelberg@web.de>
To: buildroot@busybox.net
Subject: [Buildroot] [GIT PULL] avr32 updates
Date: Sat, 9 May 2009 10:50:04 +0200 [thread overview]
Message-ID: <200905091050.04559.markus.heidelberg@web.de> (raw)
In-Reply-To: <87ab5oapss.fsf@macbook.be.48ers.dk>
Peter Korsgaard, 08.05.2009:
> >>>>> "Thiago" == Thiago A Corr?a <thiago.correa@gmail.com> writes:
> Thiago> Anyway, what happens if I apply a patch and then you apply it
> Thiago> a while later before pulling from my tree? I guess we will
> Thiago> conflict right?
>
> No, if none of us modify the patch then the git sha1 id will be the
> same
No, it will be different because of the different committer identity.
> and the commit just ignored (if one of us modifies it you will
> most likely get a merge conflict that you'll have to resolve when you
> rebase your changes against me).
If the changes are the same, there will be no merge conflict, it will be
resolved automatically. But it won't ignore a commit, it will leave 2
commits with the same change in the repository, which may be confusing
when browsing the history.
Markus
next prev parent reply other threads:[~2009-05-09 8:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-08 4:52 [Buildroot] [GIT PULL] avr32 updates Thiago A. Corrêa
2009-05-08 7:13 ` Peter Korsgaard
2009-05-08 7:59 ` Thiago A. Corrêa
2009-05-08 8:29 ` Peter Korsgaard
2009-05-08 9:17 ` Thiago A. Corrêa
2009-05-08 9:48 ` Peter Korsgaard
2009-05-08 9:57 ` Peter Korsgaard
2009-05-08 10:30 ` Peter Korsgaard
2009-05-08 10:56 ` Thiago A. Corrêa
2009-05-08 11:03 ` Daniel Mack
2009-05-08 16:59 ` Thiago A. Corrêa
2009-05-08 17:06 ` Peter Korsgaard
2009-05-09 9:18 ` Markus Heidelberg
2009-05-09 8:50 ` Markus Heidelberg [this message]
2009-05-12 10:30 ` Peter Korsgaard
2009-05-12 17:33 ` Thiago A. Corrêa
2009-05-12 19:46 ` Peter Korsgaard
2009-05-12 20:09 ` Thiago A. Corrêa
2009-05-12 20:27 ` Peter Korsgaard
2009-05-08 7:15 ` Peter Korsgaard
2009-05-08 8:25 ` Daniel Mack
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=200905091050.04559.markus.heidelberg@web.de \
--to=markus.heidelberg@web.de \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox