From: Junio C Hamano <junkio@cox.net>
To: Eygene Ryabinkin <rea-git@codelabs.ru>
Cc: Andy Parkins <andyparkins@gmail.com>,
Alex Riesen <raa.lkml@gmail.com>,
git@vger.kernel.org,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: Memory overrun in http-push.c
Date: Thu, 01 Mar 2007 04:08:20 -0800 [thread overview]
Message-ID: <7vr6s9qi8b.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20070301120042.GD63606@codelabs.ru> (Eygene Ryabinkin's message of "Thu, 1 Mar 2007 15:00:42 +0300")
Eygene Ryabinkin <rea-git@codelabs.ru> writes:
> Good day!
>
>> was more annoyed by the fact that the patch was an attachment,
>> than it was generated by diff without leading a/ and b/ paths.
>
> So, git is unable to use this type of patches directly and I will
> need to do
> $ patch < patchfile
> $ rm file.orig
> $ git commit
In case it was unclear, I was saying that "attachment was more
annoying" than "diff output that does not follow the established
convention to be applied with patch -p1". Both I can handle,
but dealing with the former is more work for me.
next prev parent reply other threads:[~2007-03-01 12:08 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-28 15:15 Memory overrun in http-push.c Eygene Ryabinkin
2007-02-28 15:41 ` Andy Parkins
2007-02-28 15:42 ` Johannes Schindelin
2007-03-01 5:13 ` Eygene Ryabinkin
2007-03-01 8:15 ` Alex Riesen
2007-03-01 9:11 ` Eygene Ryabinkin
2007-03-01 9:21 ` Alex Riesen
2007-03-01 11:26 ` Eygene Ryabinkin
2007-03-01 9:32 ` Junio C Hamano
2007-03-01 10:04 ` Alex Riesen
2007-03-01 10:40 ` Andy Parkins
2007-03-01 12:00 ` Eygene Ryabinkin
2007-03-01 12:08 ` Junio C Hamano [this message]
2007-03-01 13:20 ` Eygene Ryabinkin
2007-03-01 17:11 ` Johannes Schindelin
2007-03-01 18:31 ` Andy Parkins
2007-03-01 18:41 ` Johannes Schindelin
2007-03-01 19:31 ` Andy Parkins
2007-03-01 20:43 ` Johannes Schindelin
2007-03-02 10:05 ` Andy Parkins
2007-03-02 14:46 ` Jakub Narebski
2007-03-02 15:22 ` Andy Parkins
2007-03-02 19:16 ` Johannes Schindelin
2007-03-02 19:42 ` Andy Parkins
2007-03-04 8:17 ` Daniel Barkalow
2007-03-04 8:31 ` Junio C Hamano
2007-03-04 9:18 ` Daniel Barkalow
2007-03-01 21:43 ` Alex Riesen
2007-03-01 21:54 ` Shawn O. Pearce
2007-03-01 17:52 ` Uwe Kleine-König
2007-03-02 14:38 ` Jakub Narebski
2007-03-02 15:17 ` Johannes Schindelin
2007-03-02 22:52 ` identifying blobs (was Re: Memory overrun in http-push.c) Junio C Hamano
2007-03-02 23:10 ` Linus Torvalds
2007-03-02 15:23 ` Memory overrun in http-push.c Andy Parkins
2007-03-02 15:30 ` Matthieu Moy
2007-03-02 15:48 ` Andy Parkins
2007-02-28 16:36 ` Florian Weimer
2007-03-01 5:19 ` Eygene Ryabinkin
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=7vr6s9qi8b.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=andyparkins@gmail.com \
--cc=git@vger.kernel.org \
--cc=raa.lkml@gmail.com \
--cc=rea-git@codelabs.ru \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.