From: Simon Marchi <simon.marchi@polymtl.ca>
To: Tom Tromey <tom@tromey.com>
Cc: Pedro Alves <palves@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [RFC] Sort #includes in gdb
Date: Fri, 29 Mar 2019 21:05:00 -0000 [thread overview]
Message-ID: <d077cc5fe3eb77bdb85ffa2ec2ca306c@polymtl.ca> (raw)
In-Reply-To: <875zs1csim.fsf@tromey.com>
On 2019-03-29 16:52, Tom Tromey wrote:
>>>>>> "Pedro" == Pedro Alves <palves@redhat.com> writes:
>
>>> I think it can't be done.
>
> Pedro> Isn't that what "try --branch" is for?
>
> No idea, but I guess the idea is to push a branch, then use "try" to do
> a try run based on that branch?
>
> I can try that. I'm a little reluctant to push a temporary branch like
> this.
> Will sourceware let me delete the branch when I'm done?
>
> Tom
We can freely push, force-push and delete the "users/*" branches. For
example, I just deleted an old branch of mine that I didn't need
anymore:
$ git push upstream :users/simark/autotools-bump
remote:
----------------------------------------------------------------------
remote: -- The hooks.no-emails config option contains
`refs/heads/users/.*',
remote: -- which matches the name of the reference being updated
remote: -- (refs/heads/users/simark/autotools-bump).
remote: --
remote: -- Commit emails will therefore not be sent.
remote:
----------------------------------------------------------------------
To ssh://sourceware.org/git/binutils-gdb.git
- [deleted] users/simark/autotools-bump
It would be fine if we did the cleanup in multiple chunks, it doesn't
have to be one big patch.
I don't think I've mentioned it, but I really like this change. I don't
like the mental weight of having to choose where to add my include in an
unorganized list :).
Simon
next prev parent reply other threads:[~2019-03-29 21:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-26 15:40 Tom Tromey
2019-01-27 4:58 ` Joel Brobecker
2019-02-15 20:46 ` Tom Tromey
2019-01-28 19:08 ` Pedro Alves
2019-01-28 22:31 ` Matt Rice
2019-02-15 20:55 ` Tom Tromey
2019-03-15 23:13 ` Tom Tromey
2019-03-20 17:42 ` Pedro Alves
2019-03-29 20:52 ` Tom Tromey
2019-03-29 21:05 ` Simon Marchi [this message]
2019-03-30 18:35 ` Tom Tromey
2019-04-03 18:58 ` Pedro Alves
2019-04-03 19:29 ` Sergio Durigan Junior
2019-04-03 20:34 ` Sergio Durigan Junior
2019-04-04 2:47 ` Tom Tromey
2019-04-04 3:40 ` Sergio Durigan Junior
2019-04-03 19:00 ` Pedro Alves
2019-04-03 20:11 ` Tom Tromey
2019-04-03 21:00 ` Pedro Alves
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=d077cc5fe3eb77bdb85ffa2ec2ca306c@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=tom@tromey.com \
/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