From: Petr Baudis <pasky@suse.cz>
To: "Lukas Sandström" <lukass@etek.chalmers.se>
Cc: Junio C Hamano <junkio@cox.net>, Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] git-am: Don't accept an mbox on stdin of we already have a .dotest directory
Date: Thu, 20 Jul 2006 16:33:54 +0200 [thread overview]
Message-ID: <20060720143353.GK13776@pasky.or.cz> (raw)
In-Reply-To: <44BE95D0.9090708@etek.chalmers.se>
Dear diary, on Wed, Jul 19, 2006 at 10:28:00PM CEST, I got a letter
where Lukas Sandström <lukass@etek.chalmers.se> said that...
> Signed-off-by: Lukas Sandström <lukass@etek.chalmers.se>
> ---
Please don't be afraid of putting stuff to commit message. It can only
improve things. :-)
> # git format-patch -k -3 master..conflict | git am -k -3
> => git-am fails with a conflict message
> # git reset --hard
>
> # git format-patch -k -3 master..ok | git am -k -3
> => git am fails with the same conflict message as above,
> => since it's trying to apply the old .dotest directory
>
> With the patch it complains about an old .dotest
> directory instead.
I think this rather means that git reset --hard should clear the .dotest
directory, or something (perhaps just warn)...
> - test ",$#," = ",0," ||
> + if test ",$#," != ",0," || ! tty -s
...but this looks like a horrible idea. Does this mean that git-am can't
be now ran without a terminal? (E.g. in a cron/at job, inside a procmail
rule etc.) That's bad.
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
Snow falling on Perl. White noise covering line noise.
Hides all the bugs too. -- J. Putnam
next prev parent reply other threads:[~2006-07-20 14:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-19 20:28 [PATCH] git-am: Don't accept an mbox on stdin of we already have a .dotest directory Lukas Sandström
2006-07-20 14:33 ` Petr Baudis [this message]
2006-07-20 19:35 ` Lukas Sandström
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=20060720143353.GK13776@pasky.or.cz \
--to=pasky@suse.cz \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=lukass@etek.chalmers.se \
/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;
as well as URLs for NNTP newsgroup(s).