Greg A. Woods [EMAIL PROTECTED] writes:
[ On Wednesday, February 2, 2005 at 15:33:28 (-0800), Mark D. Baushke wrote: ]
Subject: Re: CVS diff and unknown files.
Greg A. Woods [EMAIL PROTECTED] writes:
Yes -- we are in almost full agreement, but it cannot use '-n'. (no
commitinfo
[ On Wednesday, February 2, 2005 at 12:08:54 (-0800), Paul Sander wrote: ]
Subject: Re: CVS diff and unknown files.
So while you believe that add-time hooks are folly, there's another
half of the community that thinks they're very useful. Sergei, in the
SCM world, there are many issues
[ On Wednesday, February 2, 2005 at 15:33:28 (-0800), Mark D. Baushke wrote: ]
Subject: Re: CVS diff and unknown files.
Greg A. Woods [EMAIL PROTECTED] writes:
Yes -- we are in almost full agreement, but it cannot use '-n'. (no
commitinfo scripts are run with '-n' and I don't think
On Feb 1, 2005, at 8:16 AM, [EMAIL PROTECTED] wrote:
Paul Sander [EMAIL PROTECTED] writes:
On Jan 31, 2005, at 9:30 AM, [EMAIL PROTECTED] wrote:
That's not to say that we will *always* know at add time that the
commit will fail; failures can occur due to problems in their
content
which are
On Feb 1, 2005, at 12:03 PM, [EMAIL PROTECTED] wrote:
[ On Saturday, January 29, 2005 at 15:22:34 (-0800), Paul Sander
wrote: ]
Subject: Re: Triggers (was Re: CVS diff and unknown files.)
You don't seem to understand the fact that cvs add and cvs rm are
supposed to be exactly the same as vi
Greg A. Woods [EMAIL PROTECTED] writes:
[ On , January 31, 2005 at 20:30:21 (+0300), Sergei Organov wrote: ]
Subject: Re: CVS diff and unknown files.
Don't you wish to even try to understand the suggestion? The suggestion
is: invoke *the same triggers* both at 'cvs add' and 'cvs commit
On Feb 2, 2005, at 5:02 AM, [EMAIL PROTECTED] wrote:
Greg A. Woods [EMAIL PROTECTED] writes:
[ On , January 31, 2005 at 20:30:21 (+0300), Sergei Organov wrote: ]
Subject: Re: CVS diff and unknown files.
Don't you wish to even try to understand the suggestion? The
suggestion
is: invoke *the same
[ On Wednesday, February 2, 2005 at 01:58:31 (-0800), Paul Sander wrote: ]
Subject: Re: CVS diff and unknown files.
I argue that combining add-time and commit-time
triggers is also overloading things too much.
You don't seem to understand yet that an add or rm is NO different
than any other
[ On , February 2, 2005 at 16:02:12 (+0300), Sergei Organov wrote: ]
Subject: Re: CVS diff and unknown files.
What do we exactly mean by add-time here? The time when cvs add
client command is invoked, or the time when new file is to be committed
to the repository using cvs commit?
I've
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Greg A. Woods [EMAIL PROTECTED] writes:
Yes -- we are in almost full agreement, but it cannot use '-n'. (no
commitinfo scripts are run with '-n' and I don't think they should be or
ever need to be)
I believe this statement does not reflect the
Paul Sander [EMAIL PROTECTED] writes:
On Jan 30, 2005, at 2:18 AM, [EMAIL PROTECTED] wrote:
Todd Denniston [EMAIL PROTECTED] writes:
Sergei Organov wrote:
Todd Denniston [EMAIL PROTECTED] writes:
If cvs -n commit runs the triggers to do your check(see my
question above), I have
On Feb 1, 2005, at 2:51 AM, [EMAIL PROTECTED] wrote:
Paul Sander [EMAIL PROTECTED] writes:
Would you post a message stating your point of view, completely,
please? Thanks!
I need a way to generate 'cvs diff' against read-only repository. To
achieve this it's enough to fix 'cvs add' so that it
Paul Sander [EMAIL PROTECTED] writes:
On Feb 1, 2005, at 2:51 AM, [EMAIL PROTECTED] wrote:
Paul Sander [EMAIL PROTECTED] writes:
Would you post a message stating your point of view, completely,
please? Thanks!
I need a way to generate 'cvs diff' against read-only repository. To
Paul Sander [EMAIL PROTECTED] writes:
On Jan 31, 2005, at 9:30 AM, [EMAIL PROTECTED] wrote:
[...]
Don't you wish to even try to understand the suggestion? The suggestion
is: invoke *the same triggers* both at 'cvs add' and 'cvs commit' time,
-- there is no need for separate triggers.
I
[ On Saturday, January 29, 2005 at 13:09:59 (-0800), Paul Sander wrote: ]
Subject: Re: CVS diff and unknown files.
But think about what's really going on.
You need to try harder to follow your own advice.
If
the work will be refused anyway, why would you possibly want to
deliberately
[ On Saturday, January 29, 2005 at 15:22:34 (-0800), Paul Sander wrote: ]
Subject: Re: Triggers (was Re: CVS diff and unknown files.)
But you fail to
understand the problem.
I understand the problem perfectly.
You don't seem to understand the fact that cvs add and cvs rm are
supposed
[ On Sunday, January 30, 2005 at 16:45:35 (-0800), Paul Sander wrote: ]
Subject: Re: Triggers (was Re: CVS diff and unknown files.)
It's not so unusual for people who have done SCM for many years on
large and varied projects.
Well it depends -- you seem to belong to a (hopefully small
[ On , January 31, 2005 at 20:30:21 (+0300), Sergei Organov wrote: ]
Subject: Re: CVS diff and unknown files.
Don't you wish to even try to understand the suggestion? The suggestion
is: invoke *the same triggers* both at 'cvs add' and 'cvs commit' time,
-- there is no need for separate
Paul Sander [EMAIL PROTECTED] writes:
On Jan 30, 2005, at 6:40 AM, [EMAIL PROTECTED] wrote:
Paul Sander [EMAIL PROTECTED] writes:
On Jan 28, 2005, at 8:50 AM, [EMAIL PROTECTED] wrote:
Paul Sander [EMAIL PROTECTED] writes:
On Jan 27, 2005, at 1:07 AM, [EMAIL PROTECTED] wrote:
[...]
Todd Denniston [EMAIL PROTECTED] writes:
Sergei Organov wrote:
Todd Denniston [EMAIL PROTECTED] writes:
If cvs -n commit runs the triggers to do your check(see my
question above), I have another question: in a remote server setup
(i.e., :pserver:, :ext:) which test was failed,
Paul Sander [EMAIL PROTECTED] writes:
On Jan 28, 2005, at 11:36 AM, [EMAIL PROTECTED] wrote:
[...]
If you consider my suggestion, there will be no such a beast as
add-to-working-copy-time trigger. The commit trigger will notice the
file is new and invoke appropriate additional actions (if
Paul Sander [EMAIL PROTECTED] writes:
On Jan 28, 2005, at 9:34 AM, [EMAIL PROTECTED] wrote:
Sergei Organov wrote:
Paul Sander [EMAIL PROTECTED] writes:
On Jan 27, 2005, at 1:07 AM, [EMAIL PROTECTED] wrote:
If cvs add will only warn about the problems, -- that's
OK with me as a
Paul Sander [EMAIL PROTECTED] writes:
On Jan 28, 2005, at 8:50 AM, [EMAIL PROTECTED] wrote:
Paul Sander [EMAIL PROTECTED] writes:
On Jan 27, 2005, at 1:07 AM, [EMAIL PROTECTED] wrote:
[...]
Just to understand your point better, do you propose 'cvs add -c
new_file' and 'cvs ci
[...] Sorry, I've skipped all the above.
Paul, your vision of the software world, including client/server,
wrappers, triggers, scripts, libraries, security, etc. seems to be so
unusual that it makes it very difficult to discuss these things with
you. It seems you leave in an entirely different
On Jan 30, 2005, at 2:18 AM, [EMAIL PROTECTED] wrote:
Todd Denniston [EMAIL PROTECTED] writes:
Sergei Organov wrote:
Todd Denniston [EMAIL PROTECTED] writes:
If cvs -n commit runs the triggers to do your check(see my
question above), I have another question: in a remote server setup
(i.e.,
On Jan 30, 2005, at 3:28 AM, [EMAIL PROTECTED] wrote:
Paul Sander [EMAIL PROTECTED] writes:
On Jan 28, 2005, at 11:36 AM, [EMAIL PROTECTED] wrote:
[...]
If you consider my suggestion, there will be no such a beast as
add-to-working-copy-time trigger. The commit trigger will notice the
file is new
On Jan 30, 2005, at 3:42 AM, [EMAIL PROTECTED] wrote:
Paul Sander [EMAIL PROTECTED] writes:
On Jan 28, 2005, at 9:34 AM, [EMAIL PROTECTED] wrote:
Sergei Organov wrote:
Paul Sander [EMAIL PROTECTED] writes:
On Jan 27, 2005, at 1:07 AM, [EMAIL PROTECTED] wrote:
If cvs add will only warn about the
On Jan 30, 2005, at 6:40 AM, [EMAIL PROTECTED] wrote:
Paul Sander [EMAIL PROTECTED] writes:
On Jan 28, 2005, at 8:50 AM, [EMAIL PROTECTED] wrote:
Paul Sander [EMAIL PROTECTED] writes:
On Jan 27, 2005, at 1:07 AM, [EMAIL PROTECTED] wrote:
[...]
Just to understand your point better, do you propose
On Jan 30, 2005, at 7:09 AM, [EMAIL PROTECTED] wrote:
Paul, your vision of the software world, including client/server,
wrappers, triggers, scripts, libraries, security, etc. seems to be so
unusual that it makes it very difficult to discuss these things with
you. It seems you leave in an entirely
On Jan 28, 2005, at 8:50 AM, [EMAIL PROTECTED] wrote:
Paul Sander [EMAIL PROTECTED] writes:
On Jan 27, 2005, at 1:07 AM, [EMAIL PROTECTED] wrote:
[...]
Just to understand your point better, do you propose 'cvs add -c
new_file' and 'cvs ci new_file' run exactly the same set of triggers?
Different
On Jan 28, 2005, at 9:34 AM, [EMAIL PROTECTED] wrote:
Sergei Organov wrote:
Paul Sander [EMAIL PROTECTED] writes:
On Jan 27, 2005, at 1:07 AM, [EMAIL PROTECTED] wrote:
If cvs add will only warn about the problems, -- that's
OK with me as a user.
Actually, the way I see the situation is it only
On Jan 28, 2005, at 11:36 AM, [EMAIL PROTECTED] wrote:
Todd Denniston [EMAIL PROTECTED] writes:
Sergei Organov wrote:
Paul Sander [EMAIL PROTECTED] writes:
On Jan 27, 2005, at 1:07 AM, [EMAIL PROTECTED] wrote:
[...]
Just to understand your point better, do you propose 'cvs add -c
new_file' and
On Jan 28, 2005, at 3:55 PM, [EMAIL PROTECTED] wrote:
[ On Friday, January 28, 2005 at 03:26:05 (-0800), Paul Sander wrote: ]
Subject: Triggers (was Re: CVS diff and unknown files.)
Sigh. Just because you haven't found a use for add-time triggers
within the scope of your blinders, doesn't mean
On Jan 27, 2005, at 1:07 AM, [EMAIL PROTECTED] wrote:
Paul Sander [EMAIL PROTECTED] writes:
[...]
What register adds in the repo nonsense are you talking about? The
proposal I made simply requires a contact with the server to run the
add-time triggers; it does NOT require add-time modifications of
On Jan 27, 2005, at 12:36 PM, [EMAIL PROTECTED] wrote:
[ On Wednesday, January 26, 2005 at 21:05:46 (-0800), Paul Sander
wrote: ]
Subject: Re: CVS diff and unknown files.
See above. If there are no add-time triggers, then I can live with
what you say. On the other hand, some shops REQUIRE add
Paul Sander [EMAIL PROTECTED] writes:
On Jan 27, 2005, at 1:07 AM, [EMAIL PROTECTED] wrote:
[...]
Just to understand your point better, do you propose 'cvs add -c
new_file' and 'cvs ci new_file' run exactly the same set of triggers?
Different sets?
I think the consensus in the last
Sergei Organov wrote:
Paul Sander [EMAIL PROTECTED] writes:
On Jan 27, 2005, at 1:07 AM, [EMAIL PROTECTED] wrote:
[...]
Just to understand your point better, do you propose 'cvs add -c
new_file' and 'cvs ci new_file' run exactly the same set of triggers?
Different sets?
I think
Todd Denniston [EMAIL PROTECTED] writes:
Sergei Organov wrote:
Paul Sander [EMAIL PROTECTED] writes:
On Jan 27, 2005, at 1:07 AM, [EMAIL PROTECTED] wrote:
[...]
Just to understand your point better, do you propose 'cvs add -c
new_file' and 'cvs ci new_file' run exactly the same
Sergei Organov wrote:
Todd Denniston [EMAIL PROTECTED] writes:
If cvs -n commit runs the triggers to do your check(see my question
above), I have another question: in a remote server setup (i.e., :pserver:,
:ext:) which test was failed, the add or the normal commit?
With my approach
[ On Friday, January 28, 2005 at 03:26:05 (-0800), Paul Sander wrote: ]
Subject: Triggers (was Re: CVS diff and unknown files.)
Sigh. Just because you haven't found a use for add-time triggers
within the scope of your blinders, doesn't mean that no one has.
You don't seem to understand
Paul Sander [EMAIL PROTECTED] writes:
[...]
What register adds in the repo nonsense are you talking about? The
proposal I made simply requires a contact with the server to run the
add-time triggers; it does NOT require add-time modifications of the
repository by the CVS server itself. If the
[ On Wednesday, January 26, 2005 at 21:05:46 (-0800), Paul Sander wrote: ]
Subject: Re: CVS diff and unknown files.
See above. If there are no add-time triggers, then I can live with
what you say. On the other hand, some shops REQUIRE add-time triggers,
and if add-time triggers are used
[ On , January 27, 2005 at 12:07:39 (+0300), Sergei Organov wrote: ]
Subject: Re: CVS diff and unknown files.
Well, to tell the truth, all this tagging I do would be not an issue
should CVS support changesets. The tagging in my use-cases is in fact an
attempt to somehow mark a changeset
On Jan 25, 2005, at 9:29 AM, [EMAIL PROTECTED] wrote:
Todd Denniston [EMAIL PROTECTED] writes:
Paul had a case for desiring in certain cases to contact the server
on add.
Both cases _are valid_, my desire would be for add to contact the
server
only when an extra flag is passed.
Well, I believe
[ On Wednesday, January 26, 2005 at 01:01:55 (-0800), Paul Sander wrote: ]
Subject: Re: CVS diff and unknown files.
You're falling into the same trap that Greg does, which is to think
that the way CVS works today is the way that it simply must work
(except when he has an idea to make
On Jan 26, 2005, at 11:06 AM, [EMAIL PROTECTED] wrote:
[ On Wednesday, January 26, 2005 at 01:01:55 (-0800), Paul Sander
wrote: ]
Subject: Re: CVS diff and unknown files.
You're falling into the same trap that Greg does, which is to think
that the way CVS works today is the way that it simply
for now and returning to the initial
problem, aren't there any proposals/suggested patches to add an option
to the 'cvs diff' to include unknown files into the output the same
way it now includes locally added but not committed files? Does such
extension somehow interferes with the cvs way of doing things
Todd Denniston [EMAIL PROTECTED] writes:
Sergei Organov wrote:
Paul Sander [EMAIL PROTECTED] writes:
On Jan 24, 2005, at 6:20 AM, [EMAIL PROTECTED] wrote:
SNIP
It's unclear if that particular change will be made, or if made
whether or not it will stay. The requirement to supply
[ On Saturday, January 22, 2005 at 18:59:33 (-0800), Mark D. Baushke wrote: ]
Subject: Re: CVS diff and unknown files.
cvs add does not (and must not :-) contact the server.
When I use
mkdir foo
cvs add foo
it contacts the server and creates the directory on the remote
Greg A. Woods [EMAIL PROTECTED] writes:
[ On , January 21, 2005 at 20:06:37 (+0300), [EMAIL PROTECTED] wrote: ]
Subject: CVS diff and unknown files.
Is there a way to include contents of unknown files into the 'cvs
diff' output?
I did try the -N switch but it doesn't seem to do
Sergei Organov wrote:
Greg A. Woods [EMAIL PROTECTED] writes:
[ On , January 21, 2005 at 20:06:37 (+0300), [EMAIL PROTECTED] wrote: ]
Subject: CVS diff and unknown files.
Is there a way to include contents of unknown files into the 'cvs
diff' output?
I did try the -N
Todd Denniston [EMAIL PROTECTED] writes:
[...]
$ echo dummy dummy.txt
$ cvs add -m dummy.txt
cvs [server aborted]: add requires write access to the repository
Until the Fix that Greg described late last year is put in, you can (I
think) trick cvs at least for files.
***begin
On Jan 24, 2005, at 6:20 AM, [EMAIL PROTECTED] wrote:
Todd Denniston [EMAIL PROTECTED] writes:
[...]
$ echo dummy dummy.txt
$ cvs add -m dummy.txt
cvs [server aborted]: add requires write access to the repository
Until the Fix that Greg described late last year is put in, you can (I
think) trick
Paul Sander [EMAIL PROTECTED] writes:
On Jan 24, 2005, at 6:20 AM, [EMAIL PROTECTED] wrote:
Todd Denniston [EMAIL PROTECTED] writes:
[...]
$ echo dummy dummy.txt
$ cvs add -m dummy.txt
cvs [server aborted]: add requires write access to the repository
Until the Fix that Greg
Sergei Organov writes:
Is there any sound reason why 'cvs add' and 'cvs remove' commands
require *write* access to the repo?
CVS add of a directory modifies the repository, but I suspect the actual
motivation was the principle that you should tell someone that they're
not allowed to do what
Sergei Organov wrote:
Paul Sander [EMAIL PROTECTED] writes:
On Jan 24, 2005, at 6:20 AM, [EMAIL PROTECTED] wrote:
SNIP
It's unclear if that particular change will be made, or if made
whether or not it will stay. The requirement to supply add-time
triggers has been identified (by a
[ On , January 21, 2005 at 20:06:37 (+0300), [EMAIL PROTECTED] wrote: ]
Subject: CVS diff and unknown files.
Is there a way to include contents of unknown files into the 'cvs
diff' output?
I did try the -N switch but it doesn't seem to do the trick.
You must cvs add the files before
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Greg,
Greg A. Woods [EMAIL PROTECTED] writes:
[ On , January 21, 2005 at 20:06:37 (+0300), [EMAIL PROTECTED] wrote: ]
Subject: CVS diff and unknown files.
Is there a way to include contents of unknown files into the 'cvs
diff' output
Hi,
Is there a way to include contents of unknown files into the 'cvs
diff' output?
I did try the -N switch but it doesn't seem to do the trick.
I can't 'cvs add' the files as the repository is read-only for me
(public read-only repository of an open-source project).
Thanks in advance
59 matches
Mail list logo
