public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: brobecker@adacore.com, gdb-patches@sourceware.org
Subject: Re: GDB 7.6.90 available for testing
Date: Mon, 13 Jan 2014 19:53:00 -0000	[thread overview]
Message-ID: <52D44439.2020807@redhat.com> (raw)
In-Reply-To: <83sisr66ci.fsf@gnu.org>

On 01/13/2014 07:15 PM, Eli Zaretskii wrote:
>> Date: Mon, 13 Jan 2014 20:50:28 +0200
>> From: Eli Zaretskii <eliz@gnu.org>
>> Cc: brobecker@adacore.com, gdb-patches@sourceware.org
>>
>> Is there any difference between merge and cherry-pick in this case?

merge would attempt to merge the whole of master into the branch
starting from the branching point.

> It seems msysgit's cherry-pick somehow converted gdbserver/ChangeLog
> to DOS CRLF EOL format.  So I needed one additional commit on the
> branch to fix that, before pushing.  Is that OK, or should I have done
> something different?

Ouch, sounds like a git bug...

Yeah, it would have been better if that broken EOL change
hadn't made it into the repository.  E.g., now "git blame"
on gdbserver's ChangeLog will show that commit as author
of all of the file's lines.  Luckily, as it was on the branch,
not master, it probably won't ever affect anyone.  You could,
for example, have squashed those two commits into one (with git
rebase) before pushing, ending up with a single commit that
looked just like the one in master.  Oh well, what's done is
done now.  ;-)

-- 
Pedro Alves

  reply	other threads:[~2014-01-13 19:53 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-08 10:14 Joel Brobecker
2014-01-08 18:18 ` Reini Urban
2014-01-09  2:46   ` Joel Brobecker
2014-01-09 17:07   ` Tom Tromey
2014-01-10  4:25     ` Joel Brobecker
2014-01-10  1:52   ` Yao Qi
2014-01-09 18:27 ` Regressions on s390x RHEL-6.5 (was: Re: GDB 7.6.90 available for testing) Sergio Durigan Junior
2014-01-11  8:56 ` GDB 7.6.90 available for testing Eli Zaretskii
2014-01-13 17:33   ` Eli Zaretskii
2014-01-13 17:51   ` Pedro Alves
2014-01-13 18:28     ` Eli Zaretskii
2014-01-13 18:44       ` Pedro Alves
2014-01-13 18:50         ` Eli Zaretskii
2014-01-13 19:15           ` Eli Zaretskii
2014-01-13 19:53             ` Pedro Alves [this message]
2014-01-13 20:33               ` Eli Zaretskii
2014-01-15 16:33               ` Eli Zaretskii
2014-01-13 10:29 ` Ricard Wanderlof
2014-01-13 10:37   ` Joel Brobecker

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=52D44439.2020807@redhat.com \
    --to=palves@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).