From: Cort Dougan <cort@fsmlabs.com>
To: Gabriel Paubert <paubert@iram.es>
Cc: diekema_jon <diekema@bucks.si.com>, linuxppc-embedded@lists.linuxppc.org
Subject: Re: Root keys on bk://bitkeeper.fsmlabs.com:5000 have changed
Date: Mon, 8 Jan 2001 14:21:56 -0700 [thread overview]
Message-ID: <20010108142156.Z8686@hq.fsmlabs.com> (raw)
In-Reply-To: <Pine.HPX.4.10.10101081054020.1811-100000@gra-ux1.iram.es>; from Gabriel Paubert on Mon, Jan 08, 2001 at 11:03:36AM +0100
} Nice, I have a copy of the 2.3 tree with my own patches which are quite a
} long list of changes and merges. Recloning is _not_ an option...
}
} Fortunately I was still using copy of Linus tree in my own repositories
} which I maintain personnally as my main development branch. I was
} seriously considering switching to the fsmlabs bk trees, now it will never
} happen, ever...
Changes from 2.2 to 2.3 and from 2.3 to 2.4 will not be effortless changes,
with or without any revision control. Each version is a different
repository and that's not going to change. I'm happy to see you didn't
start using the trees before you realized this (and had to put work in on
maintaining code). I'm also glad to not have you bring unreasonable
expectations to our development tree.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-01-08 21:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-06 16:50 Root keys on bk://bitkeeper.fsmlabs.com:5000 have changed diekema_jon
2001-01-06 17:47 ` Tom Rini
2001-01-06 19:39 ` Wolfgang Denk
2001-01-06 20:11 ` Tom Rini
[not found] ` <20010107031448.H13210@hq.fsmlabs.com>
[not found] ` <3A58CCC6.75B79975@mvista.com>
2001-01-08 21:22 ` Cort Dougan
2001-01-07 10:13 ` Cort Dougan
2001-01-08 10:03 ` Gabriel Paubert
2001-01-08 21:21 ` Cort Dougan [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010108142156.Z8686@hq.fsmlabs.com \
--to=cort@fsmlabs.com \
--cc=diekema@bucks.si.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=paubert@iram.es \
/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).