From: Junio C Hamano <gitster@pobox•com>
To: Derrick Stolee <derrickstolee@github•com>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail•com>,
"COGONI Guillaume" <cogoni.guillaume@gmail•com>,
Matthieu.Moy@univ-lyon1•fr, git.jonathan.bressat@gmail•com,
git@vger•kernel.org
Subject: Re: [PATCH v3 1/1] contrib/vscode/: debugging with VS Code and gdb
Date: Thu, 07 Apr 2022 09:43:24 -0700 [thread overview]
Message-ID: <xmqqmtgwu9n7.fsf@gitster.g> (raw)
In-Reply-To: <ea70aed6-7111-0795-f6d8-15deb505b1c0@github.com> (Derrick Stolee's message of "Thu, 7 Apr 2022 09:09:23 -0400")
Derrick Stolee <derrickstolee@github•com> writes:
> Sometimes, we need to meet people where they are. If they choose to
> use a proprietary editor, we can help them use that to work on our
> project.
Yes, that's a good point to make. I found that the thrust of the
suggestion made in the last part of Ævar's message was "if you are
user of VSCode, what we have in contrib/ may help your use of
debuggers in it", which was in line with the above.
>> Leaving aside completely *where* we should put such a thing I'd expect
>> something much more like:
>>
>> BEGIN QUOTE
>>
>> == Using debuggers ==
> ...
>> === GUIs ===
> ...
>
> I was trying to make a similar recommendation in my review. The point is
> not "You should use a debugger, here is VS Code", but rather ...
Yup, I guess that makes three of us?
> I think that we might want a new file where Git developers can
> share best practices and custom workflows. Such a document could
> help contributors optimize their process to their own tastes based
> on the experience of others. I can see a long list of integrations
> with editors fitting in there, along with tips like "create a RAM
> disk for running tests".
>
> My proposed name for such a file is "WorkingOnGit" but it's not
> fantastic. Suggestions welcome.
Sounds like a good thing to have, but would there truly be hints and
tips so specific to this project, I have to wonder. I do not think
we are in the business of making "how to hack on and debug a project
code that is mostly written in C and whose history is managed in
Git" tutorial for each IDE, so I am not sure how well it would fly
(not opposed to, but skeptical).
> Cogoni: In conclusion, I think that if you remove the change to
> MyFirstContribution.txt, then your patch can be merged pretty
> quickly (probably, that's not my decision). I expect this discussion
> about a potential "WorkingOnGit" file to continue, but if it comes
> to fruition, your section on VS Code would be welcome.
Yeah, the change to that document did feel like it was working at a
different level from other changes.
Thanks.
next prev parent reply other threads:[~2022-04-07 16:43 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-24 8:16 contrib/vscode/: debugging with vscode and gdb Jonathan Bressat
2022-03-25 13:19 ` Derrick Stolee
[not found] ` <2a7eecb4a0b247ef8f855f1c4fb5d510@SAMBXP02.univ-lyon1.fr>
2022-03-25 18:27 ` Matthieu Moy
2022-03-25 19:01 ` Derrick Stolee
2022-03-26 14:11 ` Jonathan Bressat
2022-04-03 20:18 ` Guillaume Cogoni
[not found] ` <7b139f2c480e4ebc8dc6615b44cd5f24@SAMBXP02.univ-lyon1.fr>
2022-04-05 9:43 ` Matthieu Moy
2022-04-05 22:45 ` [PATCH V1 0/1] contrib/vscode/: debugging with VS Code " COGONI Guillaume
2022-04-05 22:45 ` [PATCH V1 1/1] " COGONI Guillaume
2022-04-06 8:47 ` Ævar Arnfjörð Bjarmason
2022-04-06 11:59 ` Matthieu Moy
2022-04-06 13:35 ` Matthieu Moy
2022-04-06 15:18 ` [PATCH v2 0/1] " COGONI Guillaume
2022-04-06 15:18 ` [PATCH v2 1/1] " COGONI Guillaume
2022-04-06 18:03 ` Derrick Stolee
2022-04-06 20:23 ` Junio C Hamano
2022-04-06 23:39 ` [PATCH v3 0/1] " COGONI Guillaume
2022-04-06 23:39 ` [PATCH v3 1/1] " COGONI Guillaume
2022-04-07 11:17 ` Ævar Arnfjörð Bjarmason
2022-04-07 13:09 ` Derrick Stolee
2022-04-07 16:43 ` Junio C Hamano [this message]
2022-04-07 20:40 ` [PATCH v4 0/1] " COGONI Guillaume
2022-04-07 20:40 ` [PATCH v4 1/1] " COGONI Guillaume
[not found] ` <66f08cb2e81647e29a080af05d7c867e@SAMBXP02.univ-lyon1.fr>
2022-04-07 8:59 ` [PATCH V1 " Matthieu Moy
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=xmqqmtgwu9n7.fsf@gitster.g \
--to=gitster@pobox$(echo .)com \
--cc=Matthieu.Moy@univ-lyon1$(echo .)fr \
--cc=avarab@gmail$(echo .)com \
--cc=cogoni.guillaume@gmail$(echo .)com \
--cc=derrickstolee@github$(echo .)com \
--cc=git.jonathan.bressat@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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