From: Petr Baudis <pasky@ucw.cz>
To: Linus Torvalds <torvalds@osdl.org>
Cc: tony.luck@intel.com, linux-ia64@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: ia64 git pull
Date: Fri, 22 Apr 2005 02:20:43 +0200 [thread overview]
Message-ID: <20050422002043.GC1474@pasky.ji.cz> (raw)
In-Reply-To: <Pine.LNX.4.58.0504211608300.2344@ppc970.osdl.org>
Dear diary, on Fri, Apr 22, 2005 at 01:19:47AM CEST, I got a letter
where Linus Torvalds <torvalds@osdl.org> told me that...
> So in the long run this issue goes away - we'll just have synchronization
> tools that won't get any unnecessary pollution. But in the short run I
> actually check my git archive religiously for being clean, and I do
>
> fsck-cache --unreachable $(cat .git/HEAD)
>
> quite often - not because git has been flaky, but simply beause I'm anal.
> And getting objects from other branches would mess with that..
(Note that when using git-pasky, you need to do
fsck-cache --unreachable $(cat .git/heads/*)
instead.)
--
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-22 0:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200504212042.j3LKgng04318@unix-os.sc.intel.com>
[not found] ` <Pine.LNX.4.58.0504211403080.2344@ppc970.osdl.org>
[not found] ` <Pine.LNX.4.58.0504211411160.2344@ppc970.osdl.org>
2005-04-21 21:55 ` tony.luck
2005-04-21 22:29 ` Linus Torvalds
2005-04-21 22:58 ` Petr Baudis
2005-04-21 23:01 ` tony.luck
2005-04-21 23:19 ` Linus Torvalds
2005-04-22 0:19 ` Bernd Eckenfels
2005-04-22 0:20 ` Petr Baudis [this message]
2005-04-22 1:25 ` Petr Baudis
2005-04-22 1:48 ` Inaky Perez-Gonzalez
2005-04-22 1:53 ` Petr Baudis
2005-04-22 2:06 ` Inaky Perez-Gonzalez
2005-04-22 3:30 ` David A. Wheeler
2005-04-21 22:53 ` Petr Baudis
2005-04-22 3:37 ` Horst von Brand
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=20050422002043.GC1474@pasky.ji.cz \
--to=pasky@ucw.cz \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.com \
--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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®