This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [RFC] Sort #includes in gdb
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