From: David Woodhouse <dwmw2@infradead.org>
To: "Tomasz K³oczko" <kloczek@rudy.mif.pg.gda.pl>
Cc: git@vger.kernel.org, linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: empty patch-2.6.13-git? patches on ftp.kernel.org
Date: Fri, 02 Sep 2005 09:23:09 +0100 [thread overview]
Message-ID: <1125649389.6928.19.camel@baythorne.infradead.org> (raw)
In-Reply-To: <Pine.BSO.4.62.0508311527340.10416@rudy.mif.pg.gda.pl>
On Wed, 2005-08-31 at 15:34 +0200, Tomasz K³oczko wrote:
> Seems patches stored on ftp://ftp.kernel.org/pub/linux/kernel/v2.6/snapshots
> are empty (only logs are correct):
> -rw-r--r-- 1 536 536 20 Aug 30 09:01 patch-2.6.13-git1.gz
> -rw-r--r-- 1 536 536 20 Aug 31 09:01 patch-2.6.13-git2.gz
Hm. git-diff-cache now refuses to operate unless there's a local
'.git/refs' directory, even when working with a separate object
directory. So this doesn't work any more...
rm -rf tmp-empty-tree
mkdir -p tmp-empty-tree/.git
cd tmp-empty-tree
git-read-tree $CURCOMM
git-checkout-cache Makefile
perl -pi -e "s/EXTRAVERSION =.*/EXTRAVERSION = $EXTRAVERSION/" Makefile
git-diff-cache -m -p $RELTREE | gzip -9 > $STAGE/patch-$CURNAME.gz
I've changed the script to create 'tmp-empty-tree/.git/refs' and
replaced 2.6.13-git[12] with real patches.
> Also it will be good move all patch-2.6.12* and patch-2.6.13-rc* files
> from this directory to old subdirectory.
Done.
--
dwmw2
next parent reply other threads:[~2005-09-02 8:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.BSO.4.62.0508311527340.10416@rudy.mif.pg.gda.pl>
2005-09-02 8:23 ` David Woodhouse [this message]
2005-09-02 9:00 ` empty patch-2.6.13-git? patches on ftp.kernel.org Linus Torvalds
2005-09-02 9:21 ` David Woodhouse
2005-09-04 15:31 ` Jan Dittmer
2005-09-04 15:55 ` David Woodhouse
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1125649389.6928.19.camel@baythorne.infradead.org \
--to=dwmw2@infradead.org \
--cc=git@vger.kernel.org \
--cc=kloczek@rudy.mif.pg.gda.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).