From: Linus Torvalds <torvalds@osdl.org>
To: David Mansfield <david@cobite.com>
Cc: Thomas Glanzmann <sithglan@stud.uni-erlangen.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Kay Sievers <kay.sievers@vrfy.org>, Petr Baudis <pasky@ucw.cz>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: gitweb wishlist
Date: Tue, 24 May 2005 13:44:22 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.58.0505241334530.2307@ppc970.osdl.org> (raw)
In-Reply-To: <42938C5B.4000906@cobite.com>
On Tue, 24 May 2005, David Mansfield wrote:
>
> Sounds possible. Unfortunately, the 'uniqueness' of a commit actually
> doesn't exist. It's all smoke-and-mirrors. In order to disallow this
> (which I think need to do) I'd need to use some commit member
> information, and add some heuristic: if this file is already in the
> commit, then this MUST be a different commit. Unfortunately, it's
> possible that the 'member' already in the commit is the wrong one and
> this is the right one, which just sounds horribly ugly to me.
>
> I'll think on it.
I think it's a fundamentally hard problem to fix, but it may be that the
fix is to give hints about command line options and in particular the time
fuzz thing to try.
So maybe just _detection_ logic in cvsps, along with a warning like
"time fuzz is 600 seconds, and the time difference between the two
commits of this file was 431 seconds. You may want to try a lower
-z argument"
or something.
It might also be possible to try to sort all the names by date of commit
first, and see if they "bunch up" into groups of low fuzz with much bigger
fuzz in between groups..
Linus
next prev parent reply other threads:[~2005-05-24 20:41 UTC|newest]
Thread overview: 102+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-11 1:26 gitweb wishlist Petr Baudis
2005-05-11 1:49 ` YOSHIFUJI Hideaki / 吉藤英明
2005-05-11 2:04 ` Petr Baudis
2005-05-11 8:47 ` Kay Sievers
2005-05-11 9:30 ` Jan-Benedict Glaw
2005-05-14 2:39 ` Kay Sievers
2005-05-12 20:07 ` Junio C Hamano
2005-05-12 21:00 ` Kay Sievers
2005-05-12 21:18 ` Junio C Hamano
2005-06-04 8:29 ` Junio C Hamano
2005-05-13 12:06 ` Jonas Fonseca
2005-05-14 2:34 ` Kay Sievers
2005-05-14 2:43 ` Kay Sievers
2005-05-14 10:54 ` Jonas Fonseca
2005-05-18 2:55 ` Kay Sievers
2005-05-18 9:45 ` Petr Baudis
2005-05-20 16:54 ` Linus Torvalds
2005-05-20 17:04 ` Junio C Hamano
2005-05-20 17:21 ` Linus Torvalds
2005-05-20 17:58 ` Kay Sievers
2005-05-20 18:16 ` Linus Torvalds
2005-05-20 18:28 ` Linus Torvalds
2005-05-20 19:00 ` Kay Sievers
2005-05-20 19:13 ` Thomas Glanzmann
2005-05-20 19:13 ` Linus Torvalds
2005-05-20 19:22 ` Linus Torvalds
2005-05-20 20:34 ` H. Peter Anvin
2005-05-20 20:49 ` Linus Torvalds
2005-05-20 20:50 ` H. Peter Anvin
2005-05-20 21:16 ` Thomas Glanzmann
2005-05-20 22:04 ` Kay Sievers
2005-05-20 22:13 ` H. Peter Anvin
2005-05-20 23:25 ` Linus Torvalds
[not found] ` <428E745C.30304@zytor.com>
2005-05-21 0:50 ` Linus Torvalds
2005-05-21 7:35 ` cvs->git (was Re: gitweb wishlist) Matthias Urlichs
2005-05-24 3:33 ` gitweb wishlist David Mansfield
2005-05-24 3:39 ` H. Peter Anvin
2005-05-24 4:28 ` David Mansfield
2005-05-24 5:04 ` H. Peter Anvin
2005-05-24 3:52 ` Linus Torvalds
2005-05-24 8:25 ` Linus Torvalds
2005-05-24 16:00 ` Linus Torvalds
2005-05-24 16:16 ` Linus Torvalds
2005-05-24 19:54 ` David Mansfield
2005-05-24 20:03 ` David Mansfield
2005-05-24 20:10 ` David Mansfield
2005-05-24 17:08 ` David Mansfield
2005-05-24 17:28 ` Linus Torvalds
2005-05-24 18:29 ` H. Peter Anvin
2005-05-24 16:15 ` David Mansfield
2005-05-24 16:17 ` Thomas Glanzmann
2005-05-24 16:31 ` Linus Torvalds
2005-05-24 16:53 ` Linus Torvalds
2005-05-24 17:23 ` Linus Torvalds
2005-05-24 18:46 ` Thomas Glanzmann
2005-05-24 19:34 ` Linus Torvalds
2005-05-24 22:39 ` Edgar Toernig
2005-05-24 23:05 ` Linus Torvalds
2005-05-25 0:06 ` Junio C Hamano
2005-05-25 0:17 ` Linus Torvalds
2005-05-25 0:30 ` Junio C Hamano
2005-05-24 19:43 ` David Mansfield
2005-05-24 20:16 ` Thomas Glanzmann
2005-05-24 19:47 ` Linus Torvalds
2005-05-24 20:09 ` Linus Torvalds
2005-05-24 20:19 ` David Mansfield
2005-05-24 20:44 ` Linus Torvalds [this message]
2005-05-24 20:28 ` Thomas Glanzmann
2005-05-24 20:47 ` Linus Torvalds
2005-05-24 21:52 ` Thomas Glanzmann
2005-05-24 22:11 ` Linus Torvalds
2005-05-24 22:25 ` David Mansfield
2005-05-24 21:13 ` Linus Torvalds
2005-05-24 21:14 ` H. Peter Anvin
2005-05-24 21:41 ` Thomas Glanzmann
2005-05-24 21:30 ` Thomas Glanzmann
2005-05-24 21:31 ` Kay Sievers
2005-05-24 21:43 ` Linus Torvalds
2005-05-25 2:23 ` Junio C Hamano
2005-05-25 4:55 ` Linus Torvalds
2005-05-25 5:09 ` Junio C Hamano
2005-05-25 9:48 ` Kay Sievers
2005-05-25 10:54 ` David Greaves
2005-05-25 19:16 ` Junio C Hamano
2005-05-25 20:14 ` David Greaves
2005-05-25 12:35 ` Kay Sievers
2005-05-25 12:51 ` Kay Sievers
2005-05-25 19:01 ` Junio C Hamano
2005-05-25 19:01 ` Junio C Hamano
2005-05-24 20:33 ` Linus Torvalds
2005-05-24 18:29 ` Thomas Glanzmann
2005-05-24 18:52 ` Linus Torvalds
2005-05-24 19:16 ` Thomas Glanzmann
2005-05-24 19:24 ` Junio C Hamano
2005-05-24 19:44 ` Junio C Hamano
2005-05-24 20:19 ` Martin Langhoff
2005-05-24 4:58 ` Thomas Glanzmann
2005-05-26 2:51 ` David Mansfield
2005-05-20 21:41 ` Kay Sievers
2005-05-20 18:58 ` Kay Sievers
2005-05-21 7:29 ` Matthias Urlichs
2005-05-21 17:14 ` Kay Sievers
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=Pine.LNX.4.58.0505241334530.2307@ppc970.osdl.org \
--to=torvalds@osdl.org \
--cc=david@cobite.com \
--cc=git@vger.kernel.org \
--cc=hpa@zytor.com \
--cc=kay.sievers@vrfy.org \
--cc=pasky@ucw.cz \
--cc=sithglan@stud.uni-erlangen.de \
/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).