From: Junio C Hamano <junkio@cox.net>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: git@vger.kernel.org
Subject: Re: Regarding: git-lost+found
Date: Wed, 09 Nov 2005 15:23:41 -0800 [thread overview]
Message-ID: <7vwtjh8kxu.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0511091759520.25300@iabervon.org> (Daniel Barkalow's message of "Wed, 9 Nov 2005 18:06:04 -0500 (EST)")
Daniel Barkalow <barkalow@iabervon.org> writes:
> Why have git-lost+found write to files at all? It seems to me easiest to
> have the list go to standard out, and you could do "gitk `git-lost+found
> -t commit`" to see lost commits, and reconnect them as desired. (Making up
> command line syntax for listing only the commits.)
That is certainly cleaner. The only downside is fsck-objects
that lost+found uses tends to be expensive operation, and what
you would want to do with the information may be more than just
use it on the command line of gitk. But in any case the user
could store git-lost+found output in a file to do whatever she
wants, so it may not matter.
next prev parent reply other threads:[~2005-11-09 23:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-08 17:13 Regarding: git-lost+found Johannes Schindelin
2005-11-08 17:45 ` Petr Baudis
2005-11-08 17:48 ` Petr Baudis
2005-11-09 21:25 ` Junio C Hamano
2005-11-09 23:06 ` Daniel Barkalow
2005-11-09 23:23 ` Junio C Hamano [this message]
2005-11-10 0:29 ` Daniel Barkalow
2005-11-14 4:36 ` Matthias Urlichs
2005-11-14 18:01 ` Fix git-rev-list "date order" with --topo-order Linus Torvalds
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=7vwtjh8kxu.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).