Re: [drupal-devel] Re: [contributions(DRUPAL-4-5):sheldon]
On Apr 5, 2005 1:54 AM, Sheldon Rampton <sheldon@prwatch.org> wrote:
Based on my experience, I would recommend revising the contributor's guide so it doesn't advise Macintosh users to use CVL. Since I don't use Windows, I don't know whether continuing to recommend TortoiseCVS is a good idea, but if your goal is to ensure that contributors know what they're doing in CVS, I think it would be better to simply recommend using command-line access via a Unix terminal, and to provide a link to a good tutorial.
I'm a full-time Windows user (and ashamed of it, as I should be), so I followed the advice in the Drupal handbook, and used TortoiseCVS to access the repository. The handbook has very clear advice on using TortoiseCVS to download and update the repositories to your local PC (this is the simplest thing you can do with CVS). So this is what I've been using TortoiseCVS for over the past month or so: logigng in anonymously, and just grabbing all the files that are available. When I got my CVS contrib account, I tried using TortoiseCVS to make my first commit. I was too scared to do it: the handbook has no advice on how to do this (except using CLI); and there are just so many menu options you can select, and it's quite frightening, knowing that pushing many of them could potentially stuff up other people's files. So my policy now is to use command-line CVS (through Cygwin) for commits, and to use GUI CVS only for refreshing my files (anonymously). I would advise all my fellow newbie-contributors to do the same thing: only make commits using command-line CVS! Especially since the handbook (to date) only has instructions for making commits using the command-line utility. Jaza.
Jeremy Epstein wrote:
On Apr 5, 2005 1:54 AM, Sheldon Rampton <sheldon@prwatch.org> wrote:
Based on my experience, I would recommend revising the contributor's guide so it doesn't advise Macintosh users to use CVL. Since I don't use Windows, I don't know whether continuing to recommend TortoiseCVS is a good idea, ...
I'm a full-time Windows user (and ashamed of it, as I should be), so I followed the advice in the Drupal handbook, and used TortoiseCVS to access the repository. ...
When I got my CVS contrib account, I tried using TortoiseCVS to make my first commit. ...
I would advise all my fellow newbie-contributors to do the same thing: only make commits using command-line CVS! Especially since the handbook (to date) only has instructions for making commits using the command-line utility.
Let me offer a counterpoint. I don't use CVS in my day-to-day work (I much prefer the commercial software Perforce), so my goal is to learn as little CVS as possible to download Drupal and make my occasional contributions back. In the year and half that I've been involved with the Drupal project, every single CVS update *and commit* that I've made against the Drupal CVS server has been made with TortoiseCVS. As far as I can tell, they've always had exactly the effect I had intended. My work has shifted lately from Windows to Mac, but I continue to come back to Windows specifically for my downloads and uploads with Tortoise. Highly recommended. -Eric
That's nice when a PC fits into your workflow, but when you're on a portamac, TortoiseCVS is simply not an option. Not that I'm suggesting an alternative, except, perhaps, running your own personal Drumm 2.0. Chris On Apr 5, 2005 12:39 PM, Eric Scouten <drupal.org@list.ericscouten.com> wrote:
Jeremy Epstein wrote:
On Apr 5, 2005 1:54 AM, Sheldon Rampton <sheldon@prwatch.org> wrote:
Based on my experience, I would recommend revising the contributor's guide so it doesn't advise Macintosh users to use CVL. Since I don't use Windows, I don't know whether continuing to recommend TortoiseCVS is a good idea, ...
I'm a full-time Windows user (and ashamed of it, as I should be), so I followed the advice in the Drupal handbook, and used TortoiseCVS to access the repository. ...
When I got my CVS contrib account, I tried using TortoiseCVS to make my first commit. ...
I would advise all my fellow newbie-contributors to do the same thing: only make commits using command-line CVS! Especially since the handbook (to date) only has instructions for making commits using the command-line utility.
Let me offer a counterpoint.
I don't use CVS in my day-to-day work (I much prefer the commercial software Perforce), so my goal is to learn as little CVS as possible to download Drupal and make my occasional contributions back.
In the year and half that I've been involved with the Drupal project, every single CVS update *and commit* that I've made against the Drupal CVS server has been made with TortoiseCVS. As far as I can tell, they've always had exactly the effect I had intended. My work has shifted lately from Windows to Mac, but I continue to come back to Windows specifically for my downloads and uploads with Tortoise.
Highly recommended.
-Eric
Chris Messina wrote:
That's nice when a PC fits into your workflow, but when you're on a portamac, TortoiseCVS is simply not an option.
Obviously, TortoiseCVS is not for everybody. My intent was simply to disagree with Jeremy's argument that the use of visual tools should be discouraged across the board. For those people who are already using Windows, TortoiseCVS is a very good option and it works well. -Eric
Op Wednesday 06 April 2005 01:21, schreef Eric Scouten:
Obviously, TortoiseCVS is not for everybody. My intent was simply to disagree with Jeremy's argument that the use of visual tools should be discouraged across the board.
Let me add my disagreement to this pile :). I started using CVS from the commandline, and managed to break quite some stuff and loose a lot of code. I still do not really grasp it. Lets face it: CVS is very bad for branching tagging and stuff like that. So then I moved to tortoise. Not perfect, but al least the learning curve got less steep. I now use cervisia on KDE. This tool is the best GUI IMO for CVS. Not only does it always show you the CVS commands it uses for doing its magic behind the scenes (it educates me!) its settings by default are safe: If you start using it, you cannot break anything very badly. Well, unless you fiddle with the settings, but if you change advanced settings in something you dont know you are really stupid. so, yes, I plead for use of graphical tools. But that will not mean that you must no know what you are doing. Being able to click does not mean you dont have to think or read, evethough far too many ppl seem to think so. Bèr -- | Bèr Kessels | webschuur.com | website development | | Turnhoutsebaan 34/3 | 2140 Antwerpen | België | | IM: ber@jabber.org.uk | MSN: berkessels@gmx.net | | pers: bler.webschuur.com | prof: www.webschuur.com | Regards, Bèr -- [ Bèr Kessels | Drupal services www.webschuur.com ]
participants (5)
-
Bèr Kessels -
Chris Messina -
Eric Scouten -
Jeremy Epstein -
neil＠civicspacelabs.org