git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Diego Calleja <diegocg@gmail.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: git@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Linux BKCVS kernel history git import..
Date: Tue, 26 Jul 2005 21:36:43 +0200	[thread overview]
Message-ID: <20050726213643.7ca44e96.diegocg@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0507261136280.19309@g5.osdl.org>

El Tue, 26 Jul 2005 11:57:43 -0700 (PDT),
Linus Torvalds <torvalds@osdl.org> escribió:

> I'm planning on doing the 2.4 tree too some day - either as a separate
> branch in the same archive, or as a separate git archive, I haven't quite

It'd be great  to have the same thing but for the 1.0 - 2.2 tree. Of course
there are no "changelogs" for that, but incremental patches are still
available, and it'd be very interesting (for "historical reasons") to see how
things were added/removed

  reply	other threads:[~2005-07-26 19:40 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-26 18:57 Linux BKCVS kernel history git import Linus Torvalds
2005-07-26 19:36 ` Diego Calleja [this message]
2005-07-26 22:01   ` A Large Angry SCM
2005-07-27  9:40 ` David Woodhouse
2005-07-27 15:29   ` Linus Torvalds
2005-07-27 15:41     ` David Woodhouse
2005-07-27 15:50       ` Linus Torvalds
2005-07-30  8:00         ` [PATCH] Teach parse_commit_buffer about grafting Junio C Hamano
2005-07-30  8:40           ` Matthias Urlichs
2005-07-30 10:53           ` Johannes Schindelin
2005-08-18  0:30           ` Wolfgang Denk
2005-08-18  2:13             ` Junio C Hamano
2005-08-18  3:02               ` Paul Mackerras
2005-08-18  5:16                 ` Linus Torvalds
2005-08-19  0:29                   ` Paul Mackerras
2005-08-19  0:46                     ` Johannes Schindelin
2005-08-19  0:50                     ` 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=20050726213643.7ca44e96.diegocg@gmail.com \
    --to=diegocg@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=linux-kernel@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).