From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [GIT PULL] avr32 updates
Date: Tue, 12 May 2009 12:30:03 +0200 [thread overview]
Message-ID: <87y6t262c4.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <200905091050.04559.markus.heidelberg@web.de> (Markus Heidelberg's message of "Sat\, 9 May 2009 10\:50\:04 +0200")
>>>>> "Markus" == Markus Heidelberg <markus.heidelberg@web.de> writes:
Hi,
>> No, if none of us modify the patch then the git sha1 id will be the
>> same
Markus> No, it will be different because of the different committer identity.
Yes ofcourse. I meant that the file (blob) id would be identical.
Markus> If the changes are the same, there will be no merge conflict,
Markus> it will be resolved automatically. But it won't ignore a
Markus> commit, it will leave 2 commits with the same change in the
Markus> repository, which may be confusing when browsing the history.
Yeah, but if people reply to the patches with a simple "applied to my
tree, thanks" - Then that shouldn't happen often ..
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2009-05-12 10:30 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
2009-05-12 10:30 ` Peter Korsgaard [this message]
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=87y6t262c4.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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 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.