From: "Jonathan A. George" <JGeorge@greshamstorage.com>
To: Rik van Riel <riel@conectiva.com.br>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel SCM: When does CVS fall down where it REALLY matters?
Date: Thu, 07 Mar 2002 18:29:32 -0600 [thread overview]
Message-ID: <3C8805EC.3000602@greshamstorage.com> (raw)
In-Reply-To: <Pine.LNX.4.44L.0203072057510.2181-100000@imladris.surriel.com>
Rik van Riel wrote:
>On Thu, 7 Mar 2002, Jonathan A. George wrote:
>
>>I am considering adding some enhancements to CVS to address deficiencies
>>which adversely affect my productivity.
>>
>
>>... I would like to know what the Bitkeeper users consider the minimum
>>acceptable set of improvements that CVS would require for broader
>>acceptance.
>>
>
>1) working merges
>
Can you be more specific?
>2) atomic checkins of entire patches, fast tags
>
I was thinking about something like automatically tagged globally
descrete patch sets. It would then be fairly simple to create a tool
that simply scanned, merged, and checked in that patch as a set. Is
something like this what you have in mind?
>3) graphical 2-way merging tool like bitkeeper has
> (this might not seem essential to people who have
> never used it, but it has saved me many many hours)
>
Would having something like VIM or Emacs display a patch diff with
providing keystroke level merge and unmerge get toward helpful for
something like this, or is the need too complex to address that way?
>4) distributed repositories
>
Can you be more specific? (i.e. are you looking for merging,
syncronization, or copies? In other words what do you need that CVS +
rsync are unacceptable for?)
>5) ability to exchange changesets by email
>
That's a good one, and shouldn't be too bad if you like what I said for #2
>regards,
>
>Rik
>
--Jonathan--
next prev parent reply other threads:[~2002-03-08 0:31 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-07 23:51 Kernel SCM: When does CVS fall down where it REALLY matters? Jonathan A. George
2002-03-07 23:59 ` Rik van Riel
2002-03-08 0:03 ` Cort Dougan
2002-03-09 11:17 ` Roman Zippel
2002-03-09 16:45 ` Kurt Roeckx
2002-03-08 0:26 ` Andrew Morton
2002-03-08 0:36 ` Rik van Riel
2002-03-08 1:48 ` Neil Brown
2002-03-10 20:27 ` Pavel Machek
2002-03-11 21:11 ` Rik van Riel
2002-03-12 16:31 ` Pavel Machek
2002-03-08 7:37 ` Alex Riesen
2002-03-08 0:29 ` Jonathan A. George [this message]
2002-03-08 0:43 ` Rik van Riel
2002-03-08 9:32 ` Pau Aliagas
2002-03-08 16:37 ` Rik van Riel
2002-03-08 20:15 ` Pau Aliagas
2002-03-08 20:22 ` Rik van Riel
2002-03-08 20:28 ` Pau Aliagas
2002-03-08 0:38 ` Erik Andersen
2002-03-08 9:38 ` Pau Aliagas
2002-03-09 1:52 ` Val Henson
2002-03-09 2:00 ` Mike Fedyk
2002-03-09 2:25 ` Dave Jones
2002-03-08 1:19 ` Dave Jones
2002-03-08 20:27 ` Jonathan A. George
2002-03-08 21:59 ` Eli
2002-03-08 3:15 ` H. Peter Anvin
2002-03-08 9:39 ` Pau Aliagas
2002-03-11 17:05 ` Larry McVoy
2002-03-11 17:12 ` Randy.Dunlap
2002-03-11 17:25 ` Larry McVoy
2002-03-11 17:53 ` Jonathan A. George
2002-03-11 18:03 ` Larry McVoy
2002-03-11 20:36 ` Rik van Riel
2002-03-11 21:01 ` Larry McVoy
2002-03-11 21:28 ` Rik van Riel
2002-03-10 19:28 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2002-03-09 22:22 Tom Lord
2002-03-11 17:10 ` Larry McVoy
2002-03-12 6:09 ` Tom Lord
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=3C8805EC.3000602@greshamstorage.com \
--to=jgeorge@greshamstorage.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.