Louis Avrami [EMAIL PROTECTED] wrote:
On a project that I am currently working on we have a need to
implement a bug-tracking system. We would like to integrate
this bug-trakcing system with our CVS repository, primarily to
associate what source code changes
were made to fix a particular bug.
Can
On Tue, Apr 06, 2004 at 10:53:43AM -0700, Louis Avrami wrote:
Hello all,
On a project that I am currently working on we have a need to
implement a bug-tracking system. We would like to integrate
this bug-trakcing system with our CVS repository, primarily to
associate what source code changes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Louis,
Louis Avrami [EMAIL PROTECTED] writes:
Hello all,
On a project that I am currently working on we have a need to
implement a bug-tracking system. We would like to integrate
this bug-trakcing system with our CVS repository, primarily
I'm heavily invested in Lenscrafters :-)
-Original Message-
From: Terrence Enger [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 30, 2003 3:31 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: RE: Bug tracking.
At 11:15 2003-09-30 -0400, Zieg, Mark [EMAIL PROTECTED] wrote:
[snip
3. How can I apply those ten files very precisely from Dev branch to
Trunk
then to another branch?
The ideal way would be to create a tag before the bug fixes were
committed:
$ cvs tag Bugfixes-123-Before
Then commit the fixes...
$ cvs tag Bugfixes-123-Fixed
Then you can apply
At 11:15 2003-09-30 -0400, Zieg, Mark [EMAIL PROTECTED] wrote:
[snip]
You can do that easily with cvs update -j ... -j ... as long as you
create a tag each time you do the synchronization, or you can use something
like my http://www.zieg.com/pub/cvsWhoWhatWhen to extract a patchfile
scripter.
-Original Message-
From: Barry [mailto:[EMAIL PROTECTED]
Sent: Sunday, September 28, 2003 2:02 PM
To: Zieg, Mark
Subject: RE: Bug tracking.
Mark,
Sorry to send you individual email . I post the same question in
info-cvs but no replies.
I am not using any bug tracking tools yet
On Wed, Feb 05, 2003, Mark D. Baushke wrote:
I want to add a new html screen in my bug tracking tool that displays
the code of the cvs checked in files, diff of these files and cvs logs.
Can anyone point me in the right direction in terms of file names
within cvs which gathers this sort
Hiya
I want to add a new html screen in my bug tracking tool that displays the
code of the cvs checked in files, diff of these files and cvs logs.
Can anyone point me in the right direction in terms of file names within cvs
which gathers this sort of information so I can dump the relevant
Bobby Rahman [EMAIL PROTECTED] writes:
I want to add a new html screen in my bug tracking tool that displays
the code of the cvs checked in files, diff of these files and cvs logs.
Can anyone point me in the right direction in terms of file names
within cvs which gathers this sort of
Jenn Vesperman wrote:
On Thu, 2002-12-12 at 01:33, Zieg, Mark wrote:
CVS's support for bug
tracking is poor to nonexistent and many people have commented on
it and requested better support.
It already exists.
http://www.bugzilla.org/docs216/html/integration.html
snip
CVS integration is
On Tue, 2002-12-10 at 18:17, Mike Ayers wrote:
Steven Buroff wrote:
I would like to vote for this feature too.
This open source. Only patches count as votes.
CVS's support for bug
tracking is poor to nonexistent and many people have commented on
it and requested better
On Thu, 2002-12-12 at 01:33, Zieg, Mark wrote:
CVS's support for bug
tracking is poor to nonexistent and many people have commented on
it and requested better support.
That's because CVS is not a bug tracking tool. It's an archive
system. Only an archive system. If you want to
CVS's support for bug
tracking is poor to nonexistent and many people have commented on
it and requested better support.
That's because CVS is not a bug tracking tool. It's an archive
system. Only an archive system. If you want to do more than just
archiving, you must find tools
--- Forwarded mail from [EMAIL PROTECTED]
CVS's support for bug
tracking is poor to nonexistent and many people have commented on
it and requested better support.
That's because CVS is not a bug tracking tool. It's an archive
system. Only an archive system. If you want to do more
J wrote:
Well, I think you haven't tested what you are saying. Indeed, there is
I've explain it poorly prehaps.
So you can gladly go without tags: you just need to have in place an
alternate method to know that bugfix X is composed by foo.c at revision
1.2, bar.h at rev. 1.27 and
Yes, but what I would like is a uniqe commit number, whatever it may be,
578
for instance applied to all the files involved in that single commit.
It should be pretty easy to write a wrapper script around cvs commit that
does this for you, if it's really what you want:
The only trick would be
At 14:37 2002-10-11 -0500, Andrew Johnson wrote:
J wrote:
Yes, but what I would like is a uniqe commit number, whatever it may be,
578
for instance applied to all the files involved in that single commit.
That's just not how CVS works, and it never will.
Could you please tell us why think
Of
Terrence Enger
Sent: Monday, December 09, 2002 11:19 AM
To: Andrew Johnson; [EMAIL PROTECTED]
Subject: Re: Bug tracking.
At 14:37 2002-10-11 -0500, Andrew Johnson wrote:
J wrote:
Yes, but what I would like is a uniqe commit number, whatever it
may be,
578
for instance applied to all the files
I had tried once to set up a system where a number was saved withing a
CVS file, the commit would check out the file, add a BUG ID and
description and check it back in.
I had it working pretty well but got sidetracked never got back to it.
Maybe this would solve your problem.
--- Zieg, Mark
Steven Buroff wrote:
I would like to vote for this feature too.
This open source. Only patches count as votes.
CVS's support for bug
tracking is poor to nonexistent and many people have commented on
it and requested better support. Tags don't really do it.
That's because CVS is not a bug
> I am looking for some bug tracking tools that can be integrated with
CVS.
TestTrack PRo (from SeaPine) integrates with CVS. I have seen a trial
integration and do not know how well it integrates on a full scale.
-Anjali
[EMAIL PROTECTED] wrote:
Hi,
I am looking for some bug tracking tools
X-eGroups-Return: [EMAIL PROTECTED]
Date: Mon, 12 Jun 2000 21:03:49 -
From: "Jenny W" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Bug tracking systems
User-Agent: eGroups-EW/0.82
X-Mailing-List: [EMAIL PROTECTED] archive/latest/17961
We're thinking of using CVS for version control.
23 matches
Mail list logo
