From: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Jeff King <peff@peff.net>, git@vger.kernel.org
Subject: Re: [bug?] git-format-patch produces a 0-byte long patch for the first commit
Date: Tue, 24 Mar 2009 12:51:08 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.64.0903241250140.4451@axis700.grange> (raw)
In-Reply-To: <alpine.DEB.1.00.0903241244380.7493@intel-tinevez-2-302>
On Tue, 24 Mar 2009, Johannes Schindelin wrote:
> Hi,
>
> On Tue, 24 Mar 2009, Guennadi Liakhovetski wrote:
>
> > On Tue, 24 Mar 2009, Jeff King wrote:
> >
> > > On Mon, Mar 23, 2009 at 11:34:07AM +0100, Guennadi Liakhovetski wrote:
> > >
> > > > mkdir x
> > > > cd x
> > > > git-init
> > > > echo hi > greating
> > > > git-commit -a
> > > > git-format-patch -1
> > > >
> > > > produces a 0-byte long patch. git-format-patch HEAD^ produces an
> > > > error, whereas with more than one commit it produces tha last patch.
> > > > Yes, I know about "--root" and that it does allow to extract the
> > > > very first commit.
> > >
> > > What version of git are you using? I believe the 0-byte diff has been
> > > fixed since git 1.6.1.1.
> >
> > Mine is still 1.5.4, if it's already fixed in the meantime - all the
> > better!
>
> There is the off-chance that somewhere in those 3127 commits between
> v1.5.4 and v1.6.1.1, not only this bug is fixed. You might be surprised
> ;-)
>
> Seriously again, in a project that moves as fast as Git, you should always
> test with a recent version, and v1.5.1 -- being over one year old -- does
> not account for recent.
Sorry, didn't mention, I also tested with 1.6.0.6 - still was there.
Thanks
Guennadi
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer
prev parent reply other threads:[~2009-03-24 11:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-23 10:34 [bug?] git-format-patch produces a 0-byte long patch for the first commit Guennadi Liakhovetski
2009-03-23 16:29 ` Thomas Rast
2009-03-23 16:46 ` Guennadi Liakhovetski
2009-03-26 17:29 ` [PATCH] Documentation: format-patch --root clarifications Thomas Rast
2009-03-24 7:54 ` [bug?] git-format-patch produces a 0-byte long patch for the first commit Jeff King
2009-03-24 8:02 ` Guennadi Liakhovetski
2009-03-24 11:46 ` Johannes Schindelin
2009-03-24 11:51 ` Guennadi Liakhovetski [this message]
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=Pine.LNX.4.64.0903241250140.4451@axis700.grange \
--to=g.liakhovetski@gmx.de \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).