zsh-workers
 help / color / mirror / code / Atom feed
From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: "Adam Spiers" <adam@spiers.net>,
	"zsh workers mailing list" <zsh-workers@sunsite.auc.dk>
Subject: RE: PATCH: prompt fun
Date: Mon, 11 Oct 1999 17:19:10 +0400	[thread overview]
Message-ID: <000101bf13eb$345d8650$21c9ca95@mow.siemens.ru> (raw)
In-Reply-To: <19991004194029.B17010@thelonious.new.ox.ac.uk>

>
> Index: Completion/User/_prompt
> ===================================================================
> RCS file: _prompt
> diff -N _prompt
> --- /dev/null	Tue May  5 21:32:27 1998
> +++ _prompt	Mon Oct  4 18:04:35 1999

and so on

I cannot apply this patch. It creates lots of files in top-level directory. Even
with Tanaka's --use-index-line patch for patch. This is consistent - in
non-POSIX mode patch selects file name with the least number of slashes. And in
POSIX mode it won't create files.

There are more and more people using CVS on this list ... may be, we should come
up with a single patch format? This includes -p0/-p1 problem as well :-)

/andrej


  parent reply	other threads:[~1999-10-11 13:21 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-04 18:40 Adam Spiers
1999-10-04 23:14 ` Bart Schaefer
1999-10-04 23:36   ` Adam Spiers
1999-10-05  1:48     ` Mike Fletcher
1999-10-05 11:31 ` Zefram
1999-10-06 20:58   ` Adam Spiers
1999-10-07 10:43     ` Zefram
1999-10-07 13:29       ` bashprompt license (was Re: PATCH: prompt fun) Adam Spiers
1999-10-07 14:19         ` Bart Schaefer
1999-10-07 15:25           ` Oliver Kiddle
1999-10-07 16:45       ` PATCH: prompt fun Clint Adams
1999-10-07 16:49         ` Zefram
1999-10-07 17:03           ` Clint Adams
1999-10-07 17:06             ` Zefram
1999-10-11 13:19 ` Andrej Borsenkow [this message]
1999-10-11 16:39   ` Bart Schaefer
1999-10-11 21:30     ` Adam Spiers
1999-10-11 22:47       ` Bart Schaefer

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='000101bf13eb$345d8650$21c9ca95@mow.siemens.ru' \
    --to=andrej.borsenkow@mow.siemens.ru \
    --cc=adam@spiers.net \
    --cc=zsh-workers@sunsite.auc.dk \
    /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. 
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).