# Re: diff/patch (was: Re: HP OfficeJet Pro,R series support

David Paschal (paschal@ns.net)
Tue, 16 Nov 1999 02:24:32 -0800

- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
- Next message: David Paschal: "Re: Takes really long -- hp-jdex does too"
- Previous message: David Mosberger-Tang: "Re: sane and video4linux"
- Next in thread: David E. Nelson: "Re: diff/patch (was: Re: HP OfficeJet Pro,R series support"
- Reply: David E. Nelson: "Re: diff/patch (was: Re: HP OfficeJet Pro,R series support"

Thanks, David and Dave, for the info on diff and patch. My apologies for not
following up earlier. Now for a few more questions...

If I make my initial changes available in the form of a patch, then in what
form should I make further changes available? A patch to my patch, or a
patch relative to the base code I'm working from (version 0.83 of the HP
backend)? I don't want to require people to apply several patches in a row
just to get started. Mind you, I haven't gotten any feedback yet, so either
nobody has had occasion to try it out, or everything's working perfectly. :-)

Given that the HP backend seems pretty stable these days, is there even any
point in generating patches, as opposed to just providing the entirety of
the changed files? (No flames, please -- I'm just wondering!)

So how have other people dealt with branches like this without the benefit
of fancy revision control systems?

Thanks,
David Paschal
http://www.ns.net/~paschal/sane

    --
    Source code, list archive, and docs: http://www.mostang.com/sane/
    To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com

- Next message: David Paschal: "Re: Takes really long -- hp-jdex does too"
- Previous message: David Mosberger-Tang: "Re: sane and video4linux"
- Next in thread: David E. Nelson: "Re: diff/patch (was: Re: HP OfficeJet Pro,R series support"
- Reply: David E. Nelson: "Re: diff/patch (was: Re: HP OfficeJet Pro,R series support"