Doesn't the PTS also use this information to inform of vcs commits to the
suscribed users?
--
Felipe Sateler
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Hello,
On Wed, 09 May 2007, Felipe Sateler wrote:
> Doesn't the PTS also use this information to inform of vcs commits to the
> suscribed users?
No. The PTS forward VCS notifications that it receives, but it doesn't
generate them on its own. Each package/project has to setup its VCS
to send the n
On Tue, May 08, 2007 at 05:57:23PM -0500, Manoj Srivastava wrote:
> Umm, sure. I had not given an example of the control file, since
> that was the same as the control file for vim. Perhaps I need to make
> this more explicit, since you were confused.
No, it was indeed clear.
I just th
On Wed, 9 May 2007 00:07:26 +0200, Stefano Zacchiroli <[EMAIL PROTECTED]> said:
> On Tue, May 08, 2007 at 02:13:56PM -0500, Manoj Srivastava wrote:
>> The PTS already implements the fields referred to in this patch, so
>> this is a working current practice, and I think we are way past the
>> desi
On Tue, May 08, 2007 at 02:13:56PM -0500, Manoj Srivastava wrote:
> The PTS already implements the fields referred to in this patch,
> so this is a working current practice, and I think we are way past the
> design phase, so there should be no objection to including this in the
> develop
Hi,
It has been a long time since there was any discussion on this.
I have taken the last patch created by Stefano Zacchiroli, added an
arch specific example, regenerated the patch against todays CVS of the
developers reference, and attached it to this mail.
The PTS already imp
On Mon, 13 Nov 2006 17:31:32 +0100, Stefano Zacchiroli <[EMAIL PROTECTED]>
said:
> On dom, 2006-11-12 at 14:02 -0600, Manoj Srivastava wrote:
>> I suggest that we specify tow headers: and SCM specific header,
>> XS-Vcs- where name is one keyword from a specified list (bzr,
>> cvs, svn, darcs, gi
On dom, 2006-11-12 at 14:02 -0600, Manoj Srivastava wrote:
> tla is wrong. The name of the protocol is arch; and tla and
> baz are competing implementations of the standard.
Agreed, will fix this.
> I suggest that we specify tow headers: and SCM specific
> header, XS-Vcs- wher
On Sun, 2006-11-12 at 14:02 -0600, Manoj Srivastava wrote:
> I suggest that we specify tow headers: and SCM specific
> header, XS-Vcs- where name is one keyword from a specified list
> (bzr, cvs, svn, darcs, git, hf, or arch), and XS-VCS-Browse, which is
> a plain old HTTP URL.
Yes, thi
Op 12-11-2006 om 15:04 schreef Raphael Hertzog:
> On Sun, 12 Nov 2006, Geert Stappers wrote:
> > The text tells about the (upstream) source by using the generic name
> > "package", the example tells about the Debian directory.
>
> So fix the wording...
Value of this field should be an URL pointi
Hi,
in bug #391023, this description of this field is given:
+XS-Vcs-*
+
+ (where Vcs is the acronym for Version Control System,
+ and * stands for one of the Vcs supported by the package
+ tracking system: bzr, cvs, darcs,
+ git, hg, svn, tla)
+
tla is
On Sun, 12 Nov 2006, Geert Stappers wrote:
> The text tells about the (upstream) source by using the generic name
> "package", the example tells about the Debian directory.
So fix the wording... and don't change everything when there has been some
serious discussion on -devel and when lots of pack
+ XS-Vcs-Svn: svn://svn.debian.org/svn/pkg-vim/trunk/packages/vim
> +
> +
>
> Is this desciption correct?
The description leafs room for ambiguity.
The text tells about the (upstream) source by using the generic name
"package", the example tells about the Debian directory.
W
Hi,
in bug #391023, this description of this field is given:
+XS-Vcs-*
+
+ (where Vcs is the acronym for Version Control System,
+ and * stands for one of the Vcs supported by the package
+ tracking system: bzr, cvs, darcs,
+ git, hg, svn, tla)
+
+ Value of
14 matches
Mail list logo
