DragonFly BSD
DragonFly commits List (threaded) for 2005-02
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

Re: cvs commit: src/usr.bin/whois whois.c


From: "Devon H. O'Dell" <dodell@xxxxxxxxxxxxxxx>
Date: Thu, 17 Feb 2005 14:03:37 +0100

On Thu, 2005-02-17 at 13:00 +0000, David Rhodus wrote:
> On Thu, 17 Feb 2005 13:19:36 +0100, Devon H. O'Dell
> <dodell@xxxxxxxxxxxxxxx> wrote:
> > On Thu, 2005-02-17 at 03:53 -0800, Liam J. Foy wrote:
> > > liamfoy     2005/02/17 03:53:33 PST
> > >
> > > DragonFly src repository
> > >
> > >   Modified files:
> > >     usr.bin/whois        whois.c
> > >   Log:
> > >   - Better handling of a given(-p) invalid port number.
> > >
> > >   From: OpenBSD
> > 
> > Don't mean to be picky, but should we start citing revision numbers when
> > we pick something out of another tree?
> > 
> > --Devon
> > 
> > Whoops, forgot to send this to the list. I notice that lately revisions
> > aren't being cited, and it is helpful when you want to know where
> > they're from.
> > 
> > It'd be cool if the revisions could also include a link to the CVS cross
> > reference eventually, where we could give a "hint" that a revision comes
> > from another tree.
> > 
> > --Devon
> > 
> > 
> 
> I'm not sure I like that idea.  I think the commit emails are already
> too messy with the http:// links to all the diffs.  Personally when
> ever I look at pervious revision history I use cvs on the command
> line.  How many people use the http:// links in these commit emails ? 
> Perhaps we could remove them.

I do use them, since I'm not always at a machine that runs DragonFly or
has its CVS repository available, and I suspect that they're also useful
for other projects who look at the commits list for changes.

In either case, giving a hint to the XR somehow would be nice, if it was
just something that parses the commits for a From: Tree Revision-type
string.

--Devon




[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]