[Bug 226187] Merge Review: nc

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=226187





--- Comment #13 from Jan Zeleny <jzeleny at redhat.com>  2010-01-07 10:18:06 EDT ---
I have prepared another commit, but first I need to resolve the patch tracking
thing. The thing is that the situation is very similar to what you described.
Fedora took sources from OpenBSD nc and some patches are there as a result of
porting process, so in fact, we kinda have Linux fork of nc.

My point here is that describing patches and making tracking bugs for them is
IMO an unnecessary work. First reason I already wrote. Then there is the fact,
that nc upstream seems to be almost dead, there are only small changes in CVS
and they appear like twice a year. There have also been almost no big changes
in Fedora version of netcat (rebase didn't appear in last 4 years). And finally
- I don't intent to make some major changes in nc. In fact, I'd like to get
ncat to Fedora and continue major development there. For now, I want to keep nc
and maybe in time it will be appropriate to retire nc entirely.

So what do you think - should I really try to track all the patches that
haven't been tracked for years or is it ok to skip this step considering my
arguments?

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.