Fabrice commits are getting moderated, can I subscribe hime directly
or he has to do it himself ?
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
Ok,
Thanks Brett,
Arnaud
> -Message d'origine-
> De : Brett Porter [mailto:[EMAIL PROTECTED]
> Envoyé : lundi 14 novembre 2005 00:09
> À : Maven Developers List
> Objet : Re: standard form for commit messages
>
> Yes, its already under the guide for
few things going into commit messages, for
which I usually use a standard form (that matches a template
that used to exist in Apache's CVS).
Basically, wehere applicable:
PR: issue1, issue2 (using issue keys from JIRA, not URLs)
Submitted by: (when it was a patch, put that persons name
the
Hi,
Can it be documented somewhere in m1/m2 sites ?
Committers, can you try to follow it ? :-)
I took a look at recent commits and it's not really used !!
Arnaud
>
> Hi,
>
> I've noticed a few things going into commit messages, for
> which
Ok for me,
I'll try to not forget to use it ;-)
Arnaud
> -Message d'origine-
> De : Brett Porter [mailto:[EMAIL PROTECTED]
> Envoyé : vendredi 28 octobre 2005 03:46
> À : Maven Developers List
> Objet : standard form for commit messages
>
> Hi,
>
On 28/10/05, Brett Porter <[EMAIL PROTECTED]> wrote:
> PR: issue1, issue2 (using issue keys from JIRA, not URLs)
> Submitted by: (when it was a patch, put that persons name there)
> Reviewed by: (not sure if this is useful, but was in the template - who
> reviewed it)
> << comment >>
I've always w
On Thu, 2005-10-27 at 18:46 -0700, Brett Porter wrote:
> Hi,
>
> I've noticed a few things going into commit messages, for which I
> usually use a standard form (that matches a template that used to exist
> in Apache's CVS).
>
> Basically, wehere applicable:
in any other way from the issue number. I agree with the
jira issue number
On 10/27/05, Brett Porter <[EMAIL PROTECTED]> wrote:
Hi,
I've noticed a few things going into commit messages, for which I
usually use a standard form (that matches a template that used to exist
in Apache&
> Carlos Sanchez wrote:
> > I don't see the point of including the submitted by, probably it can
> > be obtained in any other way from the issue number. I agree with the
> > jira issue number
> >
> > On 10/27/05, Brett Porter <[EMAIL PROTECTED]> wrote:
>
I think the reviewed-by is pointless if it's the same person as the
committer. Otherwise, it matches exactly the template that I've been
using so far.
-Lukas
Brett Porter wrote:
Hi,
I've noticed a few things going into commit messages, for which I
usually use a standard for
> wrote:
Hi,
I've noticed a few things going into commit messages, for which I
usually use a standard form (that matches a template that used to exist
in Apache's CVS).
Basically, wehere applicable:
PR: issue1, issue2 (using issue keys from JIRA, not URLs)
Submitted by: (when it was a pa
there, I assume that each patch
will be committed separately.
Brett Porter wrote:
Hi,
I've noticed a few things going into commit messages, for which I
usually use a standard form (that matches a template that used to
exist in Apache's CVS).
Basically, wehere applicable:
PR: is
I don't see the point of including the submitted by, probably it can
be obtained in any other way from the issue number. I agree with the
jira issue number
On 10/27/05, Brett Porter <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I've noticed a few things going into commit messag
I think that's ok.
Since there is a "Submitted by: " phrase there, I assume that each patch
will be committed separately.
Brett Porter wrote:
Hi,
I've noticed a few things going into commit messages, for which I
usually use a standard form (that matches a template
Hi,
I've noticed a few things going into commit messages, for which I
usually use a standard form (that matches a template that used to exist
in Apache's CVS).
Basically, wehere applicable:
PR: issue1, issue2 (using issue keys from JIRA, not URLs)
Submitted by: (when it was a
fyi
--- Begin Message ---
Subversion commit messages are sent to different lists
according to the following mapping
# Maven
[/maven]
for_paths = maven/
to_addr = commits at maven.apache.org
suppress_if_match = yes
[/maven/continuum]
for_paths = maven/continuum/
to_addr = continuum-commits at
Subversion commit messages are sent to different lists
according to the following mapping
# Maven
[/maven]
for_paths = maven/
to_addr = commits at maven.apache.org
suppress_if_match = yes
[/maven/continuum]
for_paths = maven/continuum/
to_addr = continuum-commits at maven.apache.org
[/maven
Mark Hobson wrote:
+1 to splitting the lists - I've currently set up gmail to filter svn,
repoclean and continuum emails straight to trash ;)
Dito here.
Just for the record and to show that it is not totally unheard of, on
the Wicket project we have also split the lists:
- user
- develope
re people who are
> > interested in them can subscribe to them.
> >
> > While your work around would work, it is still a work around.
> > Splitting the traffic would be better done by putting the commit
> > messages back into their own mailing list.
> >
> >
>
terested in them can subscribe to them.
>
> While your work around would work, it is still a work around.
> Splitting the traffic would be better done by putting the commit
> messages back into their own mailing list.
>
>
> Regards,
> Alan
>
> Stephane Nicoll wrote, On 8/3/
by putting the commit
messages back into their own mailing list.
Regards,
Alan
Stephane Nicoll wrote, On 8/3/2005 12:12 AM:
Alan,
All mail clients support the creation of rules. I am personnaly using
gmail and have a forwarding rule to a specific folder for SVN commit.
I could be the trahsh
/05, Alan D. Cabrera <[EMAIL PROTECTED]> wrote:
> As it stands, it appears that all SVN commit messages are automatically
> forwarded to the developer list. Some people, like me, are not all that
> interested in the commit messages. I propose that we turn off the
> forwarding.
&g
As it stands, it appears that all SVN commit messages are automatically
forwarded to the developer list. Some people, like me, are not all that
interested in the commit messages. I propose that we turn off the
forwarding.
How this should be done is to automatically subscribe everyone in the
an overview of the issue:
-
Key: MAVEN-114
Summary: CDATA text in commit messages causes failure of changelog plugin
Type: Bug
Status: Assigned
Priority: Major
Time Spent: Unknown
Remaining: 1 day
ssue:
-
Key: MAVEN-114
Summary: CDATA text in commit messages causes failure of changelog plugin
Type: Bug
Status: Assigned
Priority: Major
Time Spent: Unknown
Remaining: 1 day
Project: maven
Fix Fors:
1.1
Assignee:
25 matches
Mail list logo
