ports/75551: [PATCH] Correct a 'post-patch' entry in the port's Makefile since a files/patch-* seems to do the same thing.
Ion-Mihai Tetcu
itetcu at people.tecnik93.com
Tue Dec 28 19:57:52 UTC 2004
On Tue, 28 Dec 2004 20:34:35 +0100
Pav Lucistnik <pav at FreeBSD.org> wrote:
> Ion-Mihai Tetcu pí¹e v út 28. 12. 2004 v 21:31 +0200:
>
> > > Second, I fear that those PRs would be forgotten in analyzed state once
> > > the port is updated and the matter settled. So I rather closed them.
> >
> > I try not to forget to say about the PRs that should be closed when my
> > PRs supersede them.
>
> Fair, I should have been more involved and track these PRs instead of
> closing them. My apology.
C'mon. You do more that enough work. If I have to use my agenda or my
company bug handling system to gain you a few minutes, that I will do.
Maybe someday, somehow I would have had (sorry, English verb times are
still something I can't master no mater what I try :-( ) contributed
enough to be a committer and then I could take acre of my own PRs, at
least :)
But why my aspell doesn't like the word 'committer' ? :))
> > > > > (Bottom line here is that you should approach maintainer directly,
> > > > > without the detour via send-pr)
> > > >
> > > > For two stylistic ones yes, but for the dir permissions (75549) and
> > > > "UntrustedDeliveryAgent" and "QuarantineAgent (75548), I tend to
> > > > believe a pr is OK.
> > >
> > > Always, always, always, when there is an active maintainer around,
> > > direct contact with a maintainer is strongly preferred.
> > >
> > > It's really an ugly habit to send-pr patch and Cc maintainer.
> >
> > Better that send pr and not cc the maintainer, anyway.
>
> Yes that's worst variant.
>
> > > First, a lot of maintainers don't know how to act properly on such
> > > emails, they just don't Cc their replies back to GNATS.
> >
> > I think the problem is that the subj, must begin with
> > FreeBSD-gnats-submit at FreeBSD.org or else it becomes a 'misfiled' reply.
^^^^^^^
I meant the 'to:'
> > Only cc'ing seems not to be enough.
>
> The trick is to leave Re: ports/XXXXX: at the beginning of the subject.
Only ? I don't think I alter the subj.Anyway next time I'll make sure.
--
IOnut
Unregistered ;) FreeBSD "user"
More information about the freebsd-ports-bugs
mailing list