From: Petr Baudis <pasky@ucw.cz>
To: Philip Pokorny <ppokorny@mindspring.com>
Cc: git@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] Cogito-0.8 (former git-pasky, big changes!)
Date: Tue, 26 Apr 2005 22:43:57 +0200 [thread overview]
Message-ID: <20050426204357.GN13224@pasky.ji.cz> (raw)
In-Reply-To: <426DE78A.3050508@mindspring.com>
Dear diary, on Tue, Apr 26, 2005 at 09:02:34AM CEST, I got a letter
where Philip Pokorny <ppokorny@mindspring.com> told me that...
> Petr Baudis wrote:
>
> >the history changed again (hopefully the
> >last time?) because of fixing dates of some old commits.
> >
>
> Looks like the git-pasky-0.7 tags (and friends) are now dead links. For
> example:
>
> [philip@xray cogito]$ cg-mkpatch git-pasky-0.7:HEAD
> .git/objects/c8/3b95297c2a6336c2007548f909769e0862b509: No such file or
> directory
> fatal: cat-file c83b95297c2a6336c2007548f909769e0862b509: bad file
> Invalid id: c83b95297c2a6336c2007548f909769e0862b509
Oops. Good catch, fixed. I actually just iterated cg-log. ;-)
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
C++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor
next prev parent reply other threads:[~2005-04-26 20:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-26 3:24 [ANNOUNCE] Cogito-0.8 (former git-pasky, big changes!) Petr Baudis
2005-04-26 3:29 ` Petr Baudis
2005-04-26 4:12 ` Mike Taht
2005-04-26 12:23 ` Petr Baudis
2005-04-26 17:40 ` Paul Jackson
2005-04-26 15:15 ` Martin Atukunda
2005-04-26 4:22 ` Benjamin Herrenschmidt
2005-04-26 4:58 ` Jeff Garzik
2005-04-26 5:18 ` Daniel Barkalow
2005-04-26 5:40 ` Al Viro
2005-04-26 6:03 ` [PATCH] Don't use commit-id in building Daniel Barkalow
2005-04-26 7:02 ` [ANNOUNCE] Cogito-0.8 (former git-pasky, big changes!) Philip Pokorny
2005-04-26 20:43 ` Petr Baudis [this message]
2005-04-26 13:36 ` Morten Welinder
2005-04-26 22:21 ` Pavel Machek
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=20050426204357.GN13224@pasky.ji.cz \
--to=pasky@ucw.cz \
--cc=git@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ppokorny@mindspring.com \
/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).