[pdp7-unix] pdp7-unix Digest, Vol 5, Issue 6

Will Senn will.senn at gmail.com
Sun Oct 20 00:21:48 AEST 2019

On 10/18/19 9:00 PM, pdp7-unix-request at minnie.tuhs.org wrote:
> Message: 2 Date: Fri, 18 Oct 2019 18:03:16 -0400 From: Phil Budne 
> <phil at ultimate.com> To: pdp7-unix at minnie.tuhs.org Subject: Re: 
> [pdp7-unix] pull requests help Message-ID: 
> <201910182203.x9IM3G6b029085 at ultimate.com> Content-Type: text/plain; 
> charset=us-ascii
>> but what's the procedure?
> The usual way is: "fork" the repo (makes a clone under your user id at
> github) by clicking on the "tuning fork" at the top left of the
> screen.
> Clone that repo down to your working system.
> I recommend making a branch off of master, and doing work there.
> Push the branch up to your github account with "git push"
> Open the web page for the repo in your github account.
> Select your working branch.
> Click on "New Pull Request"
> If you need to catch your repo up to the state of the DoctorWkt repo,
> I add it to my working repo as a remote named "upstream"
> Then I can do:
> git checkout master
> git pull upstream
> This should always run cleanly if you never modify your master branch!
> To bring a branch up to a modern state, you can then rebase it from
> your local master.
This is helpful. Wish me luck. I should add some files this afternoon. 
Is scans the right destination for new files from pdf to text?


GPG Fingerprint: 68F4 B3BD 1730 555A 4462  7D45 3EAA 5B6D A982 BAAF

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/pdp7-unix/attachments/20191019/bb3e27c1/attachment.html>

More information about the pdp7-unix mailing list