From: Dave Jones <davej@redhat.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: nightly tarballs of git
Date: Sat, 16 Sep 2006 13:58:53 -0400 [thread overview]
Message-ID: <20060916175853.GA24124@redhat.com> (raw)
In-Reply-To: <7virjq2oyc.fsf@assigned-by-dhcp.cox.net>
On Thu, Sep 14, 2006 at 01:06:03PM -0700, Junio C Hamano wrote:
> If you are using git-tar-tree (which by the way _is_ the right
> thing to do) and if you are just taking an upstream snapshot
> without doing your own development (which also is the case
> here), then you do not even need a working tree in the directory
> this script runs. It would save your disk space and time to
> check out the updated working tree files.
>
> Perhaps...
>
> #!/bin/sh
> URL=git://git.kernel.org/pub/scm/git/git.git
> PROJ=git
>
> cd ~/git-trees
> if test -d "$PROJ"
> then
> cd "$PROJ" && git fetch
> else
> git clone -q -n "$URL" "$PROJ" && cd "$PROJ"
> fi || {
> echo >&2 Something wicked happend.
> exit $?
> }
> snap=git-snapshot-$(date +"%Y%m%d")
> git-tar-tree origin $snap | gzip -9 > $PROJ-$DATE.tar.gz
This went well, right up until you checked something in :-)
Generating pack...
Done counting 155 objects.
Result has 126 objects.
Deltifying 126 objects.
0% (1/126) done
1% (2/126) done
2% (3/126) done
3% (4/126) done
4% (6/126) done
5% (7/126) done
6% (8/126) done
7% (9/126) done
8% (11/126) done
9% (12/126) done
10% (13/126) done
11% (14/126) done
12% (16/126) done
13% (17/126) done
14% (18/126) done
15% (19/126) done
16% (21/126) done
17% (22/126) done
18% (23/126) done
19% (24/126) done
20% (26/126) done
21% (27/126) done
22% (28/126) done
23% (29/126) done
24% (31/126) done
25% (32/126) done
26% (33/126) done
27% (35/126) done
28% (36/126) done
29% (37/126) done
30% (38/126) done
31% (40/126) done
32% (41/126) done
33% (42/126) done
34% (43/126) done
35% (45/126) done
36% (46/126) done
37% (47/126) done
38% (48/126) done
39% (50/126) done
40% (51/126) done
41% (52/126) done
42% (53/126) done
43% (55/126) done
44% (56/126) done
45% (57/126) done
46% (58/126) done
47% (60/126) done
48% (61/126) done
49% (62/126) done
50% (63/126) done
51% (65/126) done
52% (66/126) done
53% (67/126) done
54% (69/126) done
55% (70/126) done
56% (71/126) done
57% (72/126) done
58% (74/126) done
59% (75/126) done
60% (76/126) done
61% (77/126) done
62% (79/126) done
63% (80/126) done
64% (81/126) done
65% (82/126) done
66% (84/126) done
67% (85/126) done
68% (86/126) done
69% (87/126) done
70% (89/126) done
71% (90/126) done
72% (91/126) done
73% (92/126) done
74% (94/126) done
75% (95/126) done
76% (96/126) done
77% (98/126) done
78% (99/126) done
79% (100/126) done
80% (101/126) done
81% (103/126) done
82% (104/126) done
83% (105/126) done
84% (106/126) done
85% (108/126) done
86% (109/126) done
87% (110/126) done
88% (111/126) done
89% (113/126) done
90% (114/126) done
91% (115/126) done
92% (116/126) done
93% (118/126) done
94% (119/126) done
95% (120/126) done
96% (121/126) done
97% (123/126) done
98% (124/126) done
99% (125/126) done
100% (126/126) done
Unpacking 126 objects
Total 126, written 126 (delta 93), reused 0 (delta 0)
* refs/heads/origin: fast forward to branch 'master' of git://git.kernel.org/pub/scm/git/git
from 38529e28a4f465ad5d5f2fa249ca17da680bac5f to fc2b2be031f44aef0106cf7f872b750cd90b2253
* refs/heads/pu: does not fast forward to branch 'pu' of git://git.kernel.org/pub/scm/git/git;
not updating.
Something wicked happend.
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2006-09-16 17:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060914172754.GF8013@us.ibm.com>
2006-09-14 17:51 ` nightly tarballs of git Dave Jones
2006-09-14 19:15 ` Junio C Hamano
2006-09-14 19:36 ` Dave Jones
2006-09-14 19:48 ` Jakub Narebski
2006-09-14 20:06 ` Junio C Hamano
2006-09-16 17:58 ` Dave Jones [this message]
2006-09-16 18:04 ` Jakub Narebski
2006-09-16 18:09 ` Junio C Hamano
2006-09-17 0:03 ` Dave Jones
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=20060916175853.GA24124@redhat.com \
--to=davej@redhat.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.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).