From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00
	autolearn=unavailable autolearn_force=no version=3.4.4
Path: 
 eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: Keith Thompson <kst-u@mib.org>
Newsgroups: comp.lang.ada
Subject: Re: ANN: Awesome-Ada
Date: Wed, 05 Dec 2018 22:51:11 -0800
Organization: None to speak of
Message-ID: <ln36rbkv1c.fsf@kst-u.example.com>
References: <9cc33ea4-0164-4568-9295-c051342aed23@googlegroups.com>
	<3790db70-0f76-4f33-8ded-642dfeae9ca3@googlegroups.com>
	<c53e0a0e-0470-47b0-ac1e-b2c66c9372ec@googlegroups.com>
	<b0922657-300e-49bf-90ab-1da48e83a854@googlegroups.com>
	<d36c0344-17d9-4da5-a2cf-01995d990faf@googlegroups.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Injection-Info: reader01.eternal-september.org;
 posting-host="c1f90fdc7f96d5c1497475e112934118";
	logging-data="12731"; mail-complaints-to="abuse@eternal-september.org";
	posting-account="U2FsdGVkX1+Oj2WXWTi+xAohjVZC5dpO"
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux)
Cancel-Lock: sha1:3mama3hnXSMBCQxmUrZOBItltZE=
	sha1:W16pNbvJiScaM8Batjz/IR05sok=
Xref: reader01.eternal-september.org comp.lang.ada:54971
Date: 2018-12-05T22:51:11-08:00
List-Id: <comp.lang.ada>

Jere <jhb.chat@gmail.com> writes:
> On Wednesday, December 5, 2018 at 11:13:59 AM UTC-5, Olivier Henley wrote:
>> Done.
>> 
>> Next time, try directly on github.
>> 
>> Fabien Chouteau:
>> 
>> For README's and other markdown files, it is easier to make the
>> modification and pull requests directly on GitHub website.
>> 
>> When looking at a file:
>> https://github.com/ohenley/awesome-ada/blob/master/README.md
>> 
>> You have a pen icon to clone and edit the file.
>
> I saw that, but when I hovered over the tooltip, it said it would fork 
> the repo.  I wasn't really wanting to fork it necessarily.  I'm glad to 
> provide updates here and there, but don't want to maintain a separate
> fork of the repo.  Or is the fork more of a "temporary" fork that goes
> away after making the change?

A fork is (or acts like) a full copy (clone) of a repo.  It doesn't
go away until and unless you choose to delete it.  GitHub probably
has infrastructure to make forking a relatively cheap operation,
not creating a full copy of the repo -- though you can create such
a copy on your own system by cloning the forked repo.

-- 
Keith Thompson (The_Other_Keith) kst@mib.org  <http://www.ghoti.net/~kst>
Will write code for food.
"We must do something.  This is something.  Therefore, we must do this."
    -- Antony Jay and Jonathan Lynn, "Yes Minister"