From: Keith Packard <keithp@keithp.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: keithp@keithp.com, Git Mailing List <git@vger.kernel.org>
Subject: Re: [RFC] Make dot-counting ignore ".1" at the end
Date: Wed, 22 Mar 2006 23:17:50 -0800 [thread overview]
Message-ID: <1143098270.6850.29.camel@neko.keithp.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0603222232210.26286@g5.osdl.org>
[-- Attachment #1: Type: text/plain, Size: 867 bytes --]
On Wed, 2006-03-22 at 22:34 -0800, Linus Torvalds wrote:
> With that in place (the "make sure we have a proper ancestor branch"
> thing), a "git cvsimport" of the binutils tree seems to be working, at
> least to the point that it seems to have imported 1400+ commits without
> undue complaints. But hey, I'm looking forward to something less
> hacked-together.
Yeah, me too. Attempts at importing some of the X.org trees have
resulted in 'less than ideal' repositories.
I stuck a couple of hacks in cvsps myself to get it to deal with
X.org trees; the first was to increase a static buffer to 'large enough'
to hold X.org-style commit messages (which are enormous).
http://gitweb.freedesktop.org/?p=freedesktop-cvsps;a=summary
shows both minor patches. I should have let people know about these
earlier...
--
keith.packard@intel.com
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 191 bytes --]
next prev parent reply other threads:[~2006-03-23 7:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-23 1:29 Fix branch ancestry calculation Linus Torvalds
2006-03-23 1:50 ` [RFC] Make dot-counting ignore ".1" at the end Linus Torvalds
2006-03-23 6:26 ` Keith Packard
2006-03-23 6:34 ` Linus Torvalds
2006-03-23 7:17 ` Keith Packard [this message]
2006-03-24 14:40 ` David Mansfield
2006-03-24 14:45 ` Fix branch ancestry calculation David Mansfield
2006-03-24 15:46 ` Linus Torvalds
2006-03-24 16:38 ` Keith Packard
2006-03-25 1:45 ` Chris Shoemaker
2006-03-25 7:54 ` Keith Packard
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=1143098270.6850.29.camel@neko.keithp.com \
--to=keithp@keithp.com \
--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.
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).