Hi All,
I want to get your opinions regarding the "Commit settings" dialog.
This dialog is using the RichEdit control for entering the log message. The
problem with RichEdit is that it is quite buggy(selections and such), and it
doesn't supply the Right-click menu for CutCopyPaste. I want to
"Larry" == Larry Jones [EMAIL PROTECTED] writes:
I'm considering making some enhancements to the CVSROOT/passwd
file format and I'd like people's opinions:
First, I'd like to interpret "*" in the password field as "the
system password for this user". That would allow
Title: RE: CVSROOT/passwd enhancements
Aside from any technical issues, doesn't a * in the password field of the password file typically indicate a locked account? I realize that the CVSROOT/passwd is a different file and format but it obviously has roots to /etc/passwd. There might something
I've often wanted to check out a module, then prune off the directories
and files that
I didn't need. Until the other day I couldn't figure out a way to do it
entirely with CVS commands.
What I had been doing is deleting the directory that I didn't want, then
manually updating the CVS/Entries
On Wed, 24 May 2000, Win32 M$ wrote:
The change is a good idea, but:
OK, what if:
1. Quick solution:
I put one more button on this dialog, and then if clicked it would open
another dialog with the fonts set to let's say "Courier New 10" and the edit
box to enter the message only. After OK
On Wed, 24 May 2000, Win32 M$ wrote:
with the standard edit box (multiline). The only difference that it
makes would be that:
If you do change it PLEASE make it use Courier New 10pt (of whatever is
selected for use in the log window, and make it bigger, so that I one
could fit 80 columns of
I would love to run/try gCVS only my box has TCL 8.0 not 8.1, is there
anything that makes it 8.1 specific?
Not at all. Did you try ? I think gCvs is trying to use 8.0 (see
TclGlue.cpp).
But if you have only 8.0, you may have also a problem with GTK. GTK needs to
be 1.2.
Regards,
alex.
Formatting is not stored anyway, so there is nothing to feel sorry about.
Being able to write ChangeLog in HTML woul be useful.
Derek R. Price writes:
I noticed Larry talking about making changes to CVS and I was wondering
if somebody has been maintaining a source repository for CVS since
SourceGear bought Cyclic? Or are patches still just floating around?
I was under the impression that SourceGear had at least
[ On , May 23, 2000 at 22:25:06 (-0700), Russ Allbery wrote: ]
Subject: Re: Off topic, sort of: best ChangeLog practices?
One of the problems with abandoning ChangeLog files in favor of the commit
messages in a revision control system is that ChangeLogs have this really
valuable grouping
"Greg A. Woods" wrote:
One of the problems with ChangeLog files is that unless they are
*always* generated automatically they have a tendancy to be "different"
in unpredictable ways from the "real" logs.
Right. They aren't authoritative. I don't see that they have to be.
They can
Cameron, Steve writes:
[smc] As one who's paranoid about backups, I wonder what
measures are being taken to back up the CVS repository that
contains CVS. Even in the event of catastrophe, I'm sure somebody
will have a recent checkout of the CVS source, but it's
Someone here suggested the same thing. At first I didn't think that it updated
the parent's CVS directory, but I was wrong. It creates the file Entries.Static
which tells CVS not to update directories that aren't already checked out.
However, the method I suggested works for files, not just
We just closed an evaluation of source management systems, and the good
news is that we are sticking with CVS, Rational ClearCase lost the race. One
thing we learnt, though, from talking and reading is that a lot of ClearCase
customers take the time to define a process around the product,
Hi,
We are developing Java software and using a lot of open source components
that are all available through anon CVS. I've been thinking about how
to track these components; optimally, I'd like to stay in sync with the
"public" CVS development, while at the same time allowing local patches
to
When I first studied Unix a few years ago, I read that one should use an
asterisk to denote an impossible (i.e. unusable) password because
asterisks are not in the set of ciphertext characters used by the Unix
password encryption scheme.
On our Red Hat Linux and Solaris systems, "x" is used in
On Wed, May 24, 2000 at 03:54:11PM -0400, Avi Green wrote:
When I first studied Unix a few years ago, I read that one should use an
asterisk to denote an impossible (i.e. unusable) password because
asterisks are not in the set of ciphertext characters used by the Unix
password encryption
It seems to me that it should be possible to write something very
similar to CVSup using only the offical CVS client/server protocol,
which would allow anyone to backup any CVS repository they had access to
-- anyone looking for a project?
The protocol of choice for this seems to be
[ On Wednesday, May 24, 2000 at 14:16:10 (-0400), Larry Jones wrote: ]
Subject: Re: CVS Source Repository
It seems to me that it should be possible to write something very
similar to CVSup using only the offical CVS client/server protocol,
which would allow anyone to backup any CVS
Hi All,
OK, here is as I see it:
1. 60 chars - NO GO (see below)
2. 80 chars - NO GO (see above)
3. Non-proportional fonts, fonts choice, second dialog with Curier etc. - no
go. This is bloat.
4. To keep (1) and (2) quasi solved: Caret position box - watch your limits
by yourself!
5. To have (3)
20 matches
Mail list logo
