Re: [Groff] .cvsignore must be renamed to .gitignore

2013-12-23 Thread Eric S. Raymond
Eric S. Raymond : > Clearly I'm not awake yet (I'm fighting a bad cold and have been sleeping a > lot). I confused keyword expansion with .cvsignore conversion. That > conversion happens unconditionally, and I see a .gitignore in the > repo I pushed to Savannah. Due to a minor bug, only top-l

Re: [Groff] .cvsignore must be renamed to .gitignore

2013-12-23 Thread Eric S. Raymond
I wrote: > cvs-fast-export -k changes all .cvsignore files in the converted history > to .gitignore files, so browsing history looks like git had been in use > since the beginning. Clearly I'm not awake yet (I'm fighting a bad cold and have been sleeping a lot). I confused keyword expansion with

Re: [Groff] .cvsignore must be renamed to .gitignore

2013-12-23 Thread Eric S. Raymond
Werner LEMBERG : > > > If that's right, I could do that. > > It's correct, and thanks for doing it :-) Grmp. Apparently I forgot that switch during the conversion. Sorry. cvs-fast-export -k changes all .cvsignore files in the converted history to .gitignore files, so browsing history looks lik

Re: [Groff] .cvsignore must be renamed to .gitignore

2013-12-23 Thread Werner LEMBERG
> If that's right, I could do that. It's correct, and thanks for doing it :-) Werner

[Groff] .cvsignore must be renamed to .gitignore

2013-12-23 Thread Bernd Warken
All files `.cvsignore' should now be renamed to `.gitignore'. If that's right, I could do that. Bernd Warken

Re: [Groff] Second try at git conversion

2013-12-23 Thread Daode
Heinz-Jürgen Oertel wrote: |Am Sonntag, 22. Dezember 2013, 18:34:01 schrieb Steffen Daode Nurpmeso: |> Heinz-Jürgen Oertel wrote: |>|What would be the repository address for a git clone? |> |> git://git.savannah.gnu.org/groff.git | |all steps OK Good! (I've mailed sinuhe AT gnu.org to up

Re: [Groff] git push did not work for me

2013-12-23 Thread Bernd Warken
Yes, it works. Thanks a lot Bernd > Von: "Werner LEMBERG" > > > IO used the following commands for that purpose: > > > > git clone git://git.savannah.gnu.org/groff.git > > This is wrong. You are a user with write access, thus you have to use > > git clone bwar...@git.sv.gnu.org:/srv/git/gr

Re: [Groff] git push did not work for me

2013-12-23 Thread Werner LEMBERG
> IO used the following commands for that purpose: > > git clone git://git.savannah.gnu.org/groff.git This is wrong. You are a user with write access, thus you have to use git clone bwar...@git.sv.gnu.org:/srv/git/groff.git instead if you want to use `git push' successfully. Werner

Re: [Groff] Second try at git conversion

2013-12-23 Thread Heinz-Jürgen Oertel
Am Sonntag, 22. Dezember 2013, 18:34:01 schrieb Steffen Daode Nurpmeso: > Heinz-Jürgen Oertel wrote: > |What would be the repository address for a git clone? > > git://git.savannah.gnu.org/groff.git > > The webpage still mentions CVS only. > Ciao, > > --steffen git clone git://git.savannah.gn

[Groff] git push did not work for me

2013-12-23 Thread Bernd Warken
I tried to change groff.cpp by adding the groff option -G to the usage documentation in synopsis(). IO used the following commands for that purpose: ### git clone git://git.savannah.gnu.org/groff.git cd groff/src/roff/groff emacs groff.cpp git add groff.cpp cd ../../.. git commit git push ori