<?xml version="1.0" encoding="utf-8" ?><rss version="2.0"><channel><title>Bing: Source Code Repositories</title><link>http://www.bing.com:80/search?q=Source+Code+Repositories</link><description>Search results</description><image><url>http://www.bing.com:80/s/a/rsslogo.gif</url><title>Source Code Repositories</title><link>http://www.bing.com:80/search?q=Source+Code+Repositories</link></image><copyright>Copyright © 2026 Microsoft. All rights reserved. These XML results may not be used, reproduced or transmitted in any manner or for any purpose other than rendering Bing results within an RSS aggregator for your personal, non-commercial use. Any other use of these results requires express written permission from Microsoft Corporation. By accessing this web page or using these results in any manner whatsoever, you agree to be bound by the foregoing restrictions.</copyright><item><title>What is the difference between "." "./" and "source"?</title><link>https://unix.stackexchange.com/questions/312573/what-is-the-difference-between-and-source</link><description>The above executes the script. When the script is done, any changes that it made to the environment are discarded. . script The above sources the script. It is as if the commands had been typed in directly. Any environment changes are kept. source script This also sources the script. The source command is not required by POSIX and therefore is less portable than the shorter ..</description><pubDate>Sun, 19 Apr 2026 02:55:00 GMT</pubDate></item><item><title>Source vs . why different behaviour? - Unix &amp; Linux Stack Exchange</title><link>https://unix.stackexchange.com/questions/309768/source-vs-why-different-behaviour</link><description>source is a shell keyword that is supposed to be used like this: source file where file contains valid shell commands. These shell commands will be executed in the current shell as if typed from the command line.</description><pubDate>Sun, 19 Apr 2026 04:14:00 GMT</pubDate></item><item><title>Why can `BASH_SOURCE` be used to obtain the current directory of the ...</title><link>https://unix.stackexchange.com/questions/601074/why-can-bash-source-be-used-to-obtain-the-current-directory-of-the-executing-s</link><description>I've read that BASH_SOURCE should be populated with the name of the executing script (and it works!). But why does BASH_SOURCE hold the name of the executing script, when it is defined in man bash as an array of source filenames corresponding to shell functions?</description><pubDate>Tue, 31 Mar 2026 19:17:00 GMT</pubDate></item><item><title>OpenBSD: Where to seek for the source of programs in the base system?</title><link>https://unix.stackexchange.com/questions/563005/openbsd-where-to-seek-for-the-source-of-programs-in-the-base-system</link><description>The source code for the OpenBSD base system and the utilities that it contains is available through CVS. How you fetch the source code is described in the OpenBSD FAQ, under the section Building OpenBSD from Source.</description><pubDate>Fri, 10 Apr 2026 03:20:00 GMT</pubDate></item><item><title>Where can I get the current source code for SUSE SLES products?</title><link>https://unix.stackexchange.com/questions/701234/where-can-i-get-the-current-source-code-for-suse-sles-products</link><description>I wasn't officially asking (SUSE support) for the source code; instead it was a kind of personal initiative as the official support failed to bring forward any solution. And as said in the question: SUSE makes the source code available as demanded per GPL, but there could be a way much more convenient.</description><pubDate>Wed, 15 Apr 2026 12:54:00 GMT</pubDate></item><item><title>Conflicting values set for option Signed-By regarding source</title><link>https://unix.stackexchange.com/questions/732030/conflicting-values-set-for-option-signed-by-regarding-source</link><description>Conflicting values set for option Signed-By regarding source Ask Question Asked 3 years, 3 months ago Modified 14 days ago</description><pubDate>Mon, 20 Apr 2026 07:19:00 GMT</pubDate></item><item><title>bash source file with some modification - Unix &amp; Linux Stack Exchange</title><link>https://unix.stackexchange.com/questions/583097/bash-source-file-with-some-modification</link><description>The bigger problem I see is that bash's value for "param1" (for example) would be overwritten with the last value in the file; you haven't distinguished "section 1" from "section 2" &amp; etc.</description><pubDate>Sat, 11 Apr 2026 13:56:00 GMT</pubDate></item><item><title>Where to download Linux Kernel source code of a specific version ...</title><link>https://unix.stackexchange.com/questions/46077/where-to-download-linux-kernel-source-code-of-a-specific-version</link><description>Is there a resource to download a specific kernel version source? For example, I want to get 2.6.36.2 sources to compare with this package and see what changes were introduced?</description><pubDate>Tue, 21 Apr 2026 04:11:00 GMT</pubDate></item><item><title>convert executable back to C source code</title><link>https://unix.stackexchange.com/questions/229802/convert-executable-back-to-c-source-code</link><description>Unfortunately I lost my source code and I just have the output file that made with gcc in linux and I don’t have any access to my pc now.is there any way to convert output file to source file (in c...</description><pubDate>Wed, 22 Apr 2026 07:16:00 GMT</pubDate></item><item><title>Why does the command 'source' have that name? - Unix &amp; Linux Stack Exchange</title><link>https://unix.stackexchange.com/questions/529830/why-does-the-command-source-have-that-name</link><description>In that context, I’ve always thought of source as specifying the source of the commands the shell should execute (reverting to the current source once it’s finished). Bill Joy (who introduced source in the C shell) defined the command thus: The source command causes the shell to read commands from a specified file.</description><pubDate>Mon, 20 Apr 2026 21:31:00 GMT</pubDate></item></channel></rss>