Opened 16 years ago

Closed 16 years ago

#13395 closed enhancement (invalid)

commit message needs port name.

Reported by: frstan@… Owned by: wsiegrist@…
Priority: Normal Milestone:
Component: server/hosting Version:
Keywords: commit RSS Cc:
Port:

Description

The RSS feed would be easier to use if the port name was prefixed to the commit message. This would cause the subject line in mail (most of the time) to be sufficiently informative in itself without having to open the RSS message.

Change History (4)

comment:1 Changed 16 years ago by nox@…

Milestone: MacPorts base enhancements
Version: 1.5.2

comment:2 Changed 16 years ago by frstan@…

Ryan asked me to post the URL the RSS feed was coming from [URL]feed://cia.vc/stats/project/MacPorts/.rss[/URL]

If this is not in our control then perhaps developers could be asked to preface their commit message with "foo:" as some already do.

comment:3 Changed 16 years ago by ryandesign (Ryan Carsten Schmidt)

That URL again for clickable goodness:

feed://cia.vc/stats/project/MacPorts/.rss

I recommend developers committing changes to their ports prefix the log message with the name of the port.

Some commits affect multiple ports, so this won't always be appropriate.

Some commits are for other parts of the repository, like the web site, documentation or MacPorts base code. These commits should not be expected to have a prefix either.

You mention the subject line in mail. Are you reading this RSS feed via your email client? Or have you gotten it to send the RSS postings to your email somehow? If so, you may want to more simply subscribe to the macports-changes mailing list. Subject lines on that list are exclusively the path that was changed. The commit message is contained within the email (not in the subject).

comment:4 Changed 16 years ago by jmpp@…

Resolution: invalid
Status: newclosed

We don't control the CIA RSS feed and our own svn commit mails already contain the modified path in the subject line, therefore I'm closing this ticket as invalid.

-jmpp

Note: See TracTickets for help on using tickets.