Dear AmForthers,
long time no hear. Yes I know. All I can say is: I was very un-motivated to do
anything involving atmega microcontrollers or AmForth. When I packed
everything away in September 2020, I was very frustrated. I wanted to
implement a new version of my data collector stuff, and it
Dear AmForthers,
I have just now converted r2457 of
svn://svn.code.sf.net/p/amforth/code
via svn2git and pushed it to
https://git.sr.ht/~amforth/code/tree
If you would please be so kind as to give it a try.
Test your usual workflow.
Are all files in the expected places?
Can you assemle your
Dear AmForthers,
I forgot to "document", how I did it, in case someone else finds
this useful.
Cheers,
Erich
working on Debian 10 (buster), amd64
cd path/to/svn/working/tree
svn up
svn info
# Path: .
# Working Copy Root Path: /home/ew/eGeek/sourceforge.net/amforth-code
# URL:
Ok, found an omission,
> $ git push --set-upstream origin master
is not enough, it will push only master. So I issued
> $ git push --all
now all branches show up in
https://git.sr.ht/~amforth/code/refs
and in
git pull
git branch -a
Cheers,
Erich
Erich =?utf-8?Q?W=C3=A4lde?= writes:
> Dear
Dear Erich,
One of the easiest ways to look for the evolution of a file is
$ git log --all --graph
This lists all commits, where was changed, and rather nice ascii-art graphs.
The --all flag looks into all branches.
If you want to do more sophisticated actions per file/branch, you will have to
Dear AmForthers,
I have added the public key of Carsten Strotmann to
https://sr.ht/~amforth
This grants write access to any aspect of the repository.
I know Carsten personally since probably 2007 iirc. We first met
on the "Linux-Tag" while it was in Berlin for the first time.
Since then we
