2012/5/6 Elan Ruusamäe g...@pld-linux.org:
feel free to merge gedit2.spec to gedit.spec (and drop the former), just
remember to handle obsoletes properly
As a latecomer to CVS (backporting my knowledge of VCS from
subversion, git, etc) I am not sure which button to push here. Since
these two
On 07.05.2012 15:01, Caleb Maclennan wrote:
2012/5/6 Elan Ruusamäeg...@pld-linux.org:
feel free to merge gedit2.spec to gedit.spec (and drop the former), just
remember to handle obsoletes properly
As a latecomer to CVS (backporting my knowledge of VCS from
subversion, git, etc) I am not sure
2012/5/7 Elan Ruusamäe g...@pld-linux.org:
1. rename gedit dir to gedit0 in cvs server side and optionally drop it
client side
2. rename gedit2 dir to gedit in cvs server side, and adjust names in files
on cvs client side
This sounds good. If somebody takes care of the server side bit I'll
On 07.05.2012 16:14, Caleb Maclennan wrote:
2012/5/7 Elan Ruusamäeg...@pld-linux.org:
1. rename gedit dir to gedit0 in cvs server side and optionally drop it
client side
2. rename gedit2 dir to gedit in cvs server side, and adjust names in files
on cvs client side
This sounds good. If somebody
On 05/05/12 12:48, Caleb Maclennan wrote:
Package copied/renamed server-side.
Thank you!
Can I ask why our gedit module is called gedit2 on cvs? The upstream
project seems to be at 3.4.1, which is what we have in that spec file.
Is there any point in keeping that legacy name in our cvs module?
Package copied/renamed server-side.
Thank you!
Can I ask why our gedit module is called gedit2 on cvs? The upstream
project seems to be at 3.4.1, which is what we have in that spec file.
Is there any point in keeping that legacy name in our cvs module?
Caleb
On Fri, 04 May 2012, Caleb Maclennan wrote:
The upstream project NautilusSVN has been renamed to RabbitVCS. Can we
get our CVS module renamed or should I work on a new spec?
Package copied/renamed server-side.
cvs co packages/rabbitvcs
You can cvs rm the old package.
--
Jan Rękorajski
