Git development
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Robin Rosenberg <robin.rosenberg@dewire.com>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH 1/2] cvsexportcommit: chomp only removes trailing whitespace
Date: Wed, 14 May 2008 23:15:53 +0100 (BST)	[thread overview]
Message-ID: <alpine.DEB.1.00.0805142313280.30431@racer> (raw)
In-Reply-To: <200805142206.53242.robin.rosenberg@dewire.com>

Hi,

On Wed, 14 May 2008, Robin Rosenberg wrote:

> > Yes, that is the idea.  The point is: there are at least two different 
> > implementations of cvs, and I do not want to rely on a particular one.
> 
> Does CVSNT add extra spaces?

Probably.  At least a CR I would expect.

> A question arises. Can we use cvs update instead? It can be used to 
> retrieve the latest version (as the -u flag to cvsexportcommit does) and 
> it will tell you what status each affected file has. cvs update -n will 
> just give us the status with unambigous file names.

Will it?  The thing is: as far as I can see, cvs is only "porcelain", i.e. 
the output is meant for users' consumption, not scripts'.

So I wanted to be safe, and strip all leading and trailing whitespace, 
call "cvs status" (if necessary, in several runs, so that no ambiguous 
file names can be returned).

Ciao,
Dscho

  reply	other threads:[~2008-05-14 22:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-14 14:27 [PATCH 1/2] cvsexportcommit: chomp only removes trailing whitespace Johannes Schindelin
2008-05-14 14:29 ` [PATCH 2/2] cvsexportcommit: introduce -W for shared working trees (between Git and CVS) Johannes Schindelin
2008-05-14 17:58 ` [PATCH 1/2] cvsexportcommit: chomp only removes trailing whitespace Junio C Hamano
2008-05-14 18:38   ` Johannes Schindelin
2008-05-14 20:06     ` Robin Rosenberg
2008-05-14 22:15       ` Johannes Schindelin [this message]
2008-05-14 22:30     ` [PATCH 1/2 v2] " Johannes Schindelin
2008-05-15  2:27       ` Junio C Hamano
2008-05-15  3:21         ` Johannes Schindelin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.1.00.0805142313280.30431@racer \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=robin.rosenberg@dewire.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox