public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Sargsyan, Eduard" <eduard.sargsyan@intel.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/1] doc: update link to Oracle DTrace project
Date: Thu, 18 Jan 2024 14:23:51 +0200	[thread overview]
Message-ID: <83a5p2ygmg.fsf@gnu.org> (raw)
In-Reply-To: <SA2PR11MB4779796D6C232FC8DCAAE520E0712@SA2PR11MB4779.namprd11.prod.outlook.com> (eduard.sargsyan@intel.com)

> From: "Sargsyan, Eduard" <eduard.sargsyan@intel.com>
> CC: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
> Date: Thu, 18 Jan 2024 11:14:53 +0000
> 
> So should we use link from Wikipedia? If we want to be just replace old link, to the "same page" we probably need to use the link I have in the patch, but if we want to stay as far away from brands/commercial entities, then probably link to the Wikipedia is better. But in the second case, document reader will need to go to Wikipedia, then follow to links on the Wikipedia page.
> Or as an option we can directly use link from Wikipedia: https://dtrace.org/about/
> Which approach you find more desirable?

I prefer to link to Wikipedia, since that is unlikely to go away.  But
let's hear what others here think about this.

  reply	other threads:[~2024-01-18 12:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-19 14:44 [PATCH 0/1] The link to DTrace needs to be updated Eduard Sargsyan
2023-12-19 14:45 ` [PATCH 1/1] doc: update link to Oracle DTrace project Eduard Sargsyan
2023-12-20 11:58   ` Eli Zaretskii
2023-12-20 12:01     ` Sargsyan, Eduard
2023-12-20 13:24       ` Eli Zaretskii
2023-12-20 13:29         ` Sargsyan, Eduard
2024-01-18 11:14           ` Sargsyan, Eduard
2024-01-18 12:23             ` Eli Zaretskii [this message]
2024-01-19 16:51               ` Elena Zannoni

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=83a5p2ygmg.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=eduard.sargsyan@intel.com \
    --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).