From: Per Abrahamsen <abraham@dina.kvl.dk>
Subject: Re: Patches for cvs and cvslog
Date: Thu, 03 Jan 2002 16:24:28 +0100 [thread overview]
Message-ID: <rjsn9njw43.fsf@ssv2.dina.kvl.dk> (raw)
In-Reply-To: <m3wuyzecu6.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Thu, 03 Jan 2002 15:19:45 +0100")
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Per Abrahamsen <abraham@dina.kvl.dk> writes:
>
>> It would be nice if the user names also appeared on the summary for
>>
>> nntp+quimby.gnus.org:gnus.cvslog
>
> Yes, that would be nice.
>
> I could add a new file that had a mapping from CVS user names to From
> lines -- or names?
That would be nice. However, I just imagined something like
From: abraham <cvs@quimby.gnus.org>
you already have that information (the cvs login).
> From: Per Abrahamsen <cvs@quimby.gnus.org>
>
> Would that make sense?
>
> Or
>
> From: Per Abrahamsen <abraham@dina.kvl.dk>
>
> would probably make even more sense?
If it says "Per Abrahamsen" in the header, someone replying would
expect me to read the answer. Where does <cvs@quimby.gnus.org> end
up?
Oh, I see you already implemented the last option. Nice!
next prev parent reply other threads:[~2002-01-03 15:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-01 7:32 Lars Magne Ingebrigtsen
2002-01-02 5:27 ` Russ Allbery
2002-01-03 13:25 ` Per Abrahamsen
2002-01-03 14:19 ` Lars Magne Ingebrigtsen
2002-01-03 14:22 ` Lars Magne Ingebrigtsen
2002-01-03 15:17 ` Lars Magne Ingebrigtsen
2002-01-03 15:20 ` Lars Magne Ingebrigtsen
2002-01-03 15:30 ` Per Abrahamsen
2002-01-03 16:25 ` Lars Magne Ingebrigtsen
2002-01-03 15:30 ` Russ Allbery
2002-01-03 16:27 ` Lars Magne Ingebrigtsen
2002-01-03 16:56 ` Michael Cook
2002-02-17 0:18 ` Russ Allbery
2002-02-18 1:22 ` Lars Magne Ingebrigtsen
2002-02-18 3:32 ` Russ Allbery
2002-02-18 17:28 ` Steinar Bang
2002-01-03 15:24 ` Per Abrahamsen [this message]
2002-01-03 15:25 ` ShengHuo ZHU
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=rjsn9njw43.fsf@ssv2.dina.kvl.dk \
--to=abraham@dina.kvl.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).