• patch

    From Matt Bedynek@1:19/10 to All on Wednesday, September 02, 2015 09:47:50
    All,

    What is the process to submit a patch for husky?

    Take care,

    Matt

    ---
    * Origin: The Byte Museum - An IPV6 Capable System (1:19/10)
  • From Michael Dukelsky@2:5020/1042 to Matt Bedynek on Wednesday, September 02, 2015 21:45:30
    Hello Matt,

    Wednesday September 02 2015, Matt Bedynek wrote to All:

    What is the process to submit a patch for husky?

    In principle, you may send your patch to any admin or developer listed here: http://sourceforge.net/p/husky/_members/
    But most of them are either already out of the nodelist or not active here. So here are some persons who seem to be active:
    Michael Dukelsky 2:5020/1042,
    Gerrit Kuehn 2:240/12,
    Alexey Vissarionov 2:5020/545 (he is listed as Gremlin from Kremlin),
    Robert Clay 1:120/546.

    For example, you may send your patch to me.

    Michael

    ... node (at) f1042 (dot) ru
    --- GoldED+/LNX 1.1.5-b20100314
    * Origin: Moscow, Russia (2:5020/1042)
  • From Gerrit Kuehn@2:240/12 to Matt Bedynek on Wednesday, September 02, 2015 22:15:14
    Hello Matt!

    02 Sep 15 09:47, Matt Bedynek wrote to All:


    What is the process to submit a patch for husky?

    I guess you can simply post it here...


    Regards,
    Gerrit

    --- Msged/BSD 6.2.0
    * Origin: Dry thoughts for the tenant (2:240/12)
  • From Matt Bedynek@1:19/10 to Michael Dukelsky on Thursday, September 03, 2015 00:58:12
    Michael,

    Wednesday September 02 2015 21:45, you wrote to me:

    What is the process to submit a patch for husky?

    In principle, you may send your patch to any admin or developer listed here: http://sourceforge.net/p/husky/_members/ But most of them are
    either already out of the nodelist or not active here. So here are
    some persons who seem to be active: Michael Dukelsky
    2:5020/1042, Gerrit Kuehn 2:240/12, Alexey Vissarionov 2:5020/545 (he
    is listed as Gremlin from Kremlin), Robert Clay 1:120/546.

    For example, you may send your patch to me.

    I will send it via our link. Was going to post here for people to see but line
    wrapping is jacked up.

    Basically adds a -tooNew equivalent to the -tooOld flag.

    I have done some testing here w/o issue.

    Take care,

    Matt

    ---
    * Origin: The Byte Museum - An IPV6 Capable System (1:19/10)
  • From Matt Bedynek@1:19/10 to Gerrit Kuehn on Thursday, September 03, 2015 01:03:52
    Gerrit,

    Wednesday September 02 2015 22:15, you wrote to me:

    What is the process to submit a patch for husky?

    I guess you can simply post it here...

    It seems you have a binkp.net address. I will send to you and Mike as file attachment.

    Speaking of which, can we establish secure link?

    Take care,

    Matt

    ---
    * Origin: The Byte Museum - An IPV6 Capable System (1:19/10)
  • From Michael Dukelsky@2:5020/1042 to Matt Bedynek on Thursday, September 03, 2015 11:55:32
    Hello Matt,

    Thursday September 03 2015, Matt Bedynek wrote to Michael Dukelsky:

    I will send it via our link. Was going to post here for people to see
    but line wrapping is jacked up.

    I received it, thank you, but I did not find a change of documentaion in your diff. Please add it and please use 'diff -u'.

    Basically adds a -tooNew equivalent to the -tooOld flag.

    I do not quite understand what this feature is for. tooOld is meant to throw away messages that were kept somewhere for a long time and then
    released. They are so old that they are not interesting any more. But if a message is from the future it just means the originator failed to set
    correct time at his system. So why do we want to throw it away?

    Michael

    ... node (at) f1042 (dot) ru
    --- GoldED+/LNX 1.1.5-b20100314
    * Origin: Moscow, Russia (2:5020/1042)
  • From Matt Bedynek@1:19/10 to Michael Dukelsky on Thursday, September 03, 2015 12:21:30
    Michael,

    Thursday September 03 2015 11:55, you wrote to me:

    I do not quite understand what this feature is for. tooOld is meant to throw away messages that were kept somewhere for a long time and then released. They are so old that they are not interesting any more. But
    if a message is from the future it just means the originator failed to
    set correct time at his system. So why do we want to throw it away?

    In the past I have found that corrupted mail has bad dates. Sometimes in the past, sometimes in the future.

    I typically employ such filters here which provides a sliding window to protect
    what I toss.

    Take care,

    Matt

    ---
    * Origin: The Byte Museum - An IPV6 Capable System (1:19/10)
  • From Gerrit Kuehn@2:240/12 to Michael Dukelsky on Thursday, September 03, 2015 19:55:54
    Hello Michael!

    03 Sep 15 11:55, Michael Dukelsky wrote to Matt Bedynek:


    I received it, thank you, but I did not find a change of documentaion
    in your diff. Please add it and please use 'diff -u'.

    I must admit I was too curious to see if I could still use cvs... havn't done so for ages. Unified diff is a good point, it took me some time to remember how
    to handle rcs format (or whatever this was). I hope I didn't break anything (apologies if I did, and please feel free to revert the commit in that case). As for the documentation, I'm sure Matt can come up with a few lines for that.


    Regards,
    Gerrit

    --- Msged/BSD 6.2.0
    * Origin: We are a nation (2:240/12)
  • From Michael Dukelsky@2:5020/1042 to Gerrit Kuehn on Thursday, September 03, 2015 22:44:18
    Hello Gerrit,

    Thursday September 03 2015, Gerrit Kuehn wrote to Michael Dukelsky:

    I must admit I was too curious to see if I could still use cvs...
    havn't done so for ages. Unified diff is a good point, it took me some time to remember how to handle rcs format (or whatever this was). I
    hope I didn't break anything (apologies if I did, and please feel free
    to revert the commit in that case).

    Thank you, you made my task easier. :)

    As for the documentation, I'm sure Matt can come up with a few lines
    for that.

    Yes, he has already done it.

    Michael

    ... node (at) f1042 (dot) ru
    --- GoldED+/LNX 1.1.5-b20100314
    * Origin: Moscow, Russia (2:5020/1042)
  • From mark lewis@1:3634/12.73 to Michael Dukelsky on Thursday, September 03, 2015 18:33:38

    03 Sep 15 11:55, you wrote to Matt Bedynek:

    Basically adds a -tooNew equivalent to the -tooOld flag.

    I do not quite understand what this feature is for. tooOld is meant to throw away messages that were kept somewhere for a long time and then released. They are so old that they are not interesting any more. But
    if a message is from the future it just means the originator failed to
    set correct time at his system. So why do we want to throw it away?

    messages from the future? there's only so much future that should be allowed...
    IIRC, the normal "from the future" posting is only 24 hours... anything more than that indicates a system with a bad clock or bad software that may have a time stamp rollover problem... that or a redated regurge...

    i think you/we can check the y2k PKTDATE processor docs for more about future dated postings...

    )\/(ark

    ... Heaven won't have me. Hell thinks I'll take over.
    ---
    * Origin: (1:3634/12.73)