Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to email@example.com.
Sure, just put the $USER into the command line in taginfo, such as: ALL <your program name> $USER Then the first command parameter you will get is the user login and then the standard parameters as stated below. /Bo On Fri, 29 Nov 2002 12:36:38 -0800, "Terris Linenbach" <noreply at nowhere.nwh> wrote: >Thanks Bo! > >Is there a way to get the user that executed the command? In loginfo, for >example, you can use "$USER" as a command argument. It's unfortunate that >each line in STDIN does not include the branch tag name. > >Terris > >"Bo Berglund" <bo.berglund at telia.com> wrote in message >news:fe68uusdqvbjo9g1fr37ems45gghvc0oo2 at 4ax.com... >> On Tue, 26 Nov 2002 13:15:41 -0800, "Terris Linenbach" >> <noreply at nowhere.nwh> wrote: >> >> >Is the format roughly the same as loginfo? >> > >> As is now the case it goes like this: >> On the command line you get this: >> $1 -- tagname >> $2 -- operation "add" for tag, "mov" for tag -F, and "del" for tag -d >> $3 -- repository >> (Parameter 3 includes the full repository path down to the module >> folder, so if you are inclined you might want to filter out repository >> prefix and CVSROOT to get at the module.) >> >> Then on StdIn you get this (used to be on the command line): >> -> file revision [file revision ...] >> All spaces in filenames are escaped with a single \ >> The separator between items is a space. >> >> Have a go at it, works fine. >> >> >> /Bo >> (Bo Berglund, developer in Sweden) > /Bo (Bo Berglund, developer in Sweden)