Hello,
I've just tried using lldb on Ubuntu* and I couldn't get the command
history to work. More specifically, the command history was not
preserved between the sessions. IIUC, one has to create the lldb-history
file for this to work:
mkdir -p ~/.lldb/
touch ~/.lldb/lldb-history
This is rather
LLDB is explicitly creating the .lldb directory for the user (see Editline.cpp
-> GetHistoryFilePath). Is this also happening in a more recent LLDB version?
It’s working for me on the latest release on Arch.
> On Apr 20, 2020, at 4:34 PM, Andrzej Warzynski via lldb-dev
> wrote:
>
> Hello,
>
Cheers for your quick reply! You're probably referring to this:
https://github.com/llvm/llvm-project/blob/01bcc3e9371470e1974f066ced353df15e10056d/lldb/source/Host/common/Editline.cpp#L216
That's a fairly recent change so that explains why it didn't work for me
with lldb-8. I've also checked lld
Hi,
I wanted to continue discussing the plan to migrate from Bugzilla to Github.
It was suggested that I start a new thread and give a summary of the proposal
and what has changed since it was originally proposed in October.
== Here is the original proposal:
http://lists.llvm.org/pipermail/llvm-
On Mon, 20 Apr 2020 at 12:31, Tom Stellard via llvm-dev <
llvm-...@lists.llvm.org> wrote:
> Hi,
>
> I wanted to continue discussing the plan to migrate from Bugzilla to
> Github.
> It was suggested that I start a new thread and give a summary of the
> proposal
> and what has changed since it was o
On 04/20/2020 12:49 PM, Richard Smith wrote:
> On Mon, 20 Apr 2020 at 12:31, Tom Stellard via llvm-dev
> mailto:llvm-...@lists.llvm.org>> wrote:
>
> Hi,
>
> I wanted to continue discussing the plan to migrate from Bugzilla to
> Github.
> It was suggested that I start a new thread an
> Can we preserve the existing bug numbers if we migrate this way? There are
> lots of references to "PRx" in checked in LLVM artifacts and elsewhere in
> the world, as well as links to llvm.org/PRx, and if we can preserve all
> the issue numbers this would ease the transition pain subst
Just to clarify a bit: what I wanted to say is that it's unlikely
that we will be able to ensure that bugzilla issue numbers after
migration would coincide with github issue numbers. And therefore
proper mapping will be necessary. And this mapping would be more
complex than just rewriting the URL.
210 issues have been filed on github so far. That's negligible compared to
the total number we have, so a minor additional effort for those seems
acceptable if we can't actually clean them out and reuse the numbers.
So suppose we start with bugzilla issue #211 and migrate the issues to
github one
> If we are reasonably certain that no one would be opening new issues on
> GitHub while the migration is running...
And pull requests (the numbering is common for issues and pull
requests) as well. And we cannot disable pull requests at all. And I'm
afraid the issues will need to be opened as wel
On Mon, 20 Apr 2020 at 13:57, Anton Korobeynikov via cfe-dev <
cfe-...@lists.llvm.org> wrote:
> > If we are reasonably certain that no one would be opening new issues on
> GitHub while the migration is running...
> And pull requests (the numbering is common for issues and pull
> requests) as well.
In a previous discussion, one other suggestion had been to migrate all the
bugzilla bugs to a separate initially-private "bug archive" repository in
github. This has a few benefits:
1. If the migration is messed up, the repo can be deleted, and the process
run again, until we get a result we like.
On 2020-04-20, Richard Smith via cfe-dev wrote:
On Mon, 20 Apr 2020 at 13:57, Anton Korobeynikov via cfe-dev <
cfe-...@lists.llvm.org> wrote:
> If we are reasonably certain that no one would be opening new issues on
GitHub while the migration is running...
And pull requests (the numbering is co
On 04/20/2020 09:15 PM, Mehdi AMINI wrote:
> Hi,
>
> How is the user workflow to file bugs? Do we have some sort of template? Do
> they have to pick a label?
>
We don't have any templates defined yet, we need someone to volunteer to
do this.
Users would not be required to pick a label, they wo
On 04/20/2020 04:08 PM, James Y Knight wrote:
> In a previous discussion, one other suggestion had been to migrate all the
> bugzilla bugs to a separate initially-private "bug archive" repository in
> github. This has a few benefits:
> 1. If the migration is messed up, the repo can be deleted, an
15 matches
Mail list logo
