From: Petr Baudis <pasky@suse.cz>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Brian Gerst <bgerst@didntduck.org>, git@vger.kernel.org
Subject: Re: [PATCH] Cogito: Use git-rev-parse instead of cg-Xnormid.
Date: Mon, 4 Jul 2005 01:03:51 +0200 [thread overview]
Message-ID: <20050703230351.GE13848@pasky.ji.cz> (raw)
In-Reply-To: <Pine.LNX.4.58.0507031535420.3570@g5.osdl.org>
Dear diary, on Mon, Jul 04, 2005 at 12:40:52AM CEST, I got a letter
where Linus Torvalds <torvalds@osdl.org> told me that...
>
>
> On Sun, 3 Jul 2005, Petr Baudis wrote:
> >
> > That's right. Well, for everything but the short id matching we could
> > just check the ID validity by git-rev-parse instead of peeking into
> > the object store - I just did that.
>
> What's the format of the short ID? Minimum 6 characters of the SHA1 or
> something?
>
> Pack-files in many ways should be even easier to look up the ID in, since
> the pack-file index has all the SHA1's for that pack file listed in sorted
> order, so it should be fairly easy to just look it up based on the first
> few bytes.. If somebody sends me a patch, that should be fine.
Actually, the minimum is 4 characters, but that shouldn't be much of an
issue. Cogito's behaviour is to raise an error in case of multiple
matches; but that could be controlled by a switch too...
bash$ complete -C git-rev-parse git* cg*
I will cook up a patch in a day or two if noone outruns me.
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
<Espy> be careful, some twit might quote you out of context..
prev parent reply other threads:[~2005-07-03 23:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-03 5:59 [PATCH] Cogito: Use git-rev-parse instead of cg-Xnormid Brian Gerst
2005-07-03 6:59 ` Petr Baudis
2005-07-03 12:25 ` Brian Gerst
2005-07-03 15:41 ` Petr Baudis
2005-07-03 15:40 ` Sven Verdoolaege
2005-07-03 22:31 ` Petr Baudis
2005-07-03 22:40 ` Linus Torvalds
2005-07-03 23:03 ` Petr Baudis [this message]
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=20050703230351.GE13848@pasky.ji.cz \
--to=pasky@suse.cz \
--cc=bgerst@didntduck.org \
--cc=git@vger.kernel.org \
--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.
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).