git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] cvsserver: make the output of 'update' more compatible with cvs.

From
SOSergei Organov <osv@javad.com>
Date
Dec 7, 2009, 08:27 UTC
Message-ID
<87ocmbdw8i.fsf@osv.gnss.ru>
In-Reply-To
<20091205234831.GA925@comcast.net>
mmogilvi_git@miniinfo.net writes:
Show 25 quoted lines
> On Thu, Dec 03, 2009 at 11:12:47PM +0300, Sergei Organov wrote:
>>  
>> +    my $last_dirname = "///";
>> +    
>>      # foreach file specified on the command line ...
>>      foreach my $filename ( @{$state->{args}} )
>>      {
>>          $filename = filecleanup($filename);
>> +        my $cur_dirname = dirname($filename);
>> +        if ( $cur_dirname ne $last_dirname )
>> +        {
>> +            $last_dirname = $cur_dirname;
>> +            if ( $cur_dirname eq "" )
>> +            {
>> +                $cur_dirname = ".";
>> +            }
>> +            print "E cvs update: Updating $cur_dirname\n";
>> +        }
>>  
>>          $log->debug("Processing file $filename");
>
> This should probably be conditional on the absense of the
> global "cvs -q update" and "cvs -Q update" options, in case
> other CVS clients depend on quiet operation when they specify
> those options.
Good catch, thanks! I'll redo the patch.
-- Sergei.
Previous: mmogilvi_git@miniinfo.netNext: Sergei Organov
Message 3 of 8 in “cvsserver: make the output of 'update' more compatible with cvs.”
  1. cvsserver: make the output of 'update' more compatible with cvs.Sergei Organov, Dec 3, 2009
  2. mmogilvi_git@miniinfo.netDec 5, 2009
  3. Sergei OrganovDec 7, 2009
  4. cvsserver: make the output of 'update' more compatible with cvs.Sergei Organov, Dec 7, 2009
  5. Nanako ShiraishiDec 30, 2009
  6. Junio C HamanoDec 31, 2009
  7. Martin LanghoffDec 31, 2009
  8. Junio C HamanoDec 31, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.