mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Larry McVoy <lm@bitmover.com>
To: Ed Vance <EdV@macrolink.com>
Cc: "'Jean-Luc Leger'" <reiga@dspnet.fr.eu.org>,
	linux-kernel@vger.kernel.org
Subject: Re: Petition Against Official Endorsement of BitKeeper by Linux M aintainers
Date: Thu, 7 Mar 2002 11:06:17 -0800	[thread overview]
Message-ID: <20020307110617.C20271@work.bitmover.com> (raw)
In-Reply-To: <11E89240C407D311958800A0C9ACF7D13A76E0@EXCHANGE>
In-Reply-To: <11E89240C407D311958800A0C9ACF7D13A76E0@EXCHANGE>; from EdV@macrolink.com on Thu, Mar 07, 2002 at 10:56:08AM -0800

On Thu, Mar 07, 2002 at 10:56:08AM -0800, Ed Vance wrote:
> On Thu, Mar 07, 2002 at 10:03 AM, Jean-Luc Leger wrote:
> > > Larry McVoy <lm@bitmover.com> writes:
> > > >	bk prs -hrv2.5.0.. |  while read x
> > 
> > by the way, shouldn't it be "$x" in the second line ?
> > or am I missing something ?
> > 
> > 	JL
> 
> man bash
> ...
>     read  [-ers]  [-t  timeout]  [-a  aname]  [-p  prompt] [-n
>           nchars] [-d delim] [name ...] 

We're getting well into programming 101 and I should just shut up, but
here:

	cat > mkpatches <<EOF
	#!/bin/sh

	bk prs -hr"$1".. |  while read x
	do	bk export -tpatch -r$x > /tmp/patches/patch-$x
	done
	EOF

Yes, I believe you need cat and a Bourne compatible shell for the <<EOF
stuff and we really don't need a listing of all the shells in which this
will and will not work.

The point, which seems to be completely lost in the "I can program in 
shell better than you" discussion, is that it is trivial to export 
changes from BK as patches.  Given that the world turns on patches
today, that should be the end of the discussion and insofar as I am
concerned, it is the end of the discussion.
-- 
---
Larry McVoy            	 lm at bitmover.com           http://www.bitmover.com/lm 

  reply	other threads:[~2002-03-07 19:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-07 18:56 Ed Vance
2002-03-07 19:06 ` Larry McVoy [this message]
2002-03-07 19:06 ` Alexander Viro

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=20020307110617.C20271@work.bitmover.com \
    --to=lm@bitmover.com \
    --cc=EdV@macrolink.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reiga@dspnet.fr.eu.org \
    /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

all inboxes | Powered by JetHome®