>
> Yes. The most important git command is "git status" and tells you where
> you currently are. The preferred (=less confusing) workflow is to first
> create a branch and then start editing. There are various ways to later fix
> it, though. For example "git checkout -b my_branch" would work in
first of all, in your trac account you need the public key of your ssh
key-pair (If I lose you here, please shout!)
login to trac in the browser, go to Preferences, and select the SSH Keys
tab; paste there your id_rsa.pub from
~/.ssh/ on your local machine, and click "Save..." below the pasting
subject ought to be "...help for pushing changes to the trac's git server"
(in the era of hg it would be "... help for uploading mercurial patches to
trac")
On Friday, 5 June 2015 19:07:12 UTC+1, David Perkinson wrote:
>
> I have just made a *lot* of revisions to the files in the sage/sandpiles
On Friday, June 5, 2015 at 8:15:39 PM UTC+2, kcrisman wrote:
>
> You presumably shouldn't have to clone, I *think* every Sage copy comes
>> with a git repo at this point - is that correct, all?
>>
>
Yes. The most important git command is "git status" and tells you where you
currently are. The pre
> Once I have successfully navigated this process, I would happily provide
> feedback on the documentation. (Thanks for your tolerance with my
> questions!)
>
Opposite - thank you for your tolerance of the challenge to contribution
imposed by the new workflow. (For quick things, you can sim
Once I have successfully navigated this process, I would happily provide
feedback on the documentation. (Thanks for your tolerance with my
questions!)
On Friday, June 5, 2015 at 7:15:39 PM UTC+1, kcrisman wrote:
>
> I have just made a *lot* of revisions to the files in the sage/sandpiles/
>>
>
> I have just made a *lot* of revisions to the files in the sage/sandpiles/
> directory and would like to post then to the trac system to be reviewed and
> included in a future version of sage. I have followed the instructions
> on the "collaborative development with git-trac" page (
> htt
