kopia lustrzana https://gitlab.com/sane-project/website
55 wiersze
2.6 KiB
HTML
55 wiersze
2.6 KiB
HTML
|
<!-- received="Tue Nov 16 06:03:02 1999 PST" -->
|
|||
|
|
<!-- sent="Tue, 16 Nov 1999 09:05:38 -0600 (CST)" -->
|
|||
|
|
<!-- name="David E. Nelson" -->
|
|||
|
|
<!-- email="dnelson@jump.net" -->
|
|||
|
|
<!-- subject="Re: diff/patch (was: Re: HP OfficeJet Pro,R series support" -->
|
|||
|
|
<!-- id="" -->
|
|||
|
|
<!-- inreplyto="199911161024.CAA00975@axel.local" -->
|
|||
|
|
<title>sane-devel: Re: diff/patch (was: Re: HP OfficeJet Pro,R series support</title>
|
|||
|
|
<h1>Re: diff/patch (was: Re: HP OfficeJet Pro,R series support</h1>
|
|||
|
|
<b>David E. Nelson</b> (<a href="mailto:dnelson@jump.net"><i>dnelson@jump.net</i></a>)<br>
|
|||
|
|
<i>Tue, 16 Nov 1999 09:05:38 -0600 (CST)</i>
|
|||
|
|
<p>
|
|||
|
|
<ul>
|
|||
|
|
<li> <b>Messages sorted by:</b> <a href="date.html#151">[ date ]</a><a href="index.html#151">[ thread ]</a><a href="subject.html#151">[ subject ]</a><a href="author.html#151">[ author ]</a>
|
|||
|
|
<!-- next="start" -->
|
|||
|
|
<li> <b>Next message:</b> <a href="0152.html">Petter Reinholdtsen: "Re: sane and video4linux"</a>
|
|||
|
|
<li> <b>Previous message:</b> <a href="0150.html">David Paschal: "Re: Takes really long -- hp-jdex does too"</a>
|
|||
|
|
<li> <b>In reply to:</b> <a href="0149.html">David Paschal: "Re: diff/patch (was: Re: HP OfficeJet Pro,R series support"</a>
|
|||
|
|
<!-- nextthread="start" -->
|
|||
|
|
<!-- reply="end" -->
|
|||
|
|
</ul>
|
|||
|
|
<!-- body="start" -->
|
|||
|
|
Hi David,<br>
|
|||
|
|
<p>
|
|||
|
|
My personnal take and preference is that you start with a known base (0.83<br>
|
|||
|
|
in this case) and make two copies of it. One tree for development and one<br>
|
|||
|
|
for reference. As you make changes to the dev tree, you release one patch<br>
|
|||
|
|
at a time agaist the reference tree. Of course, you sould add versions to<br>
|
|||
|
|
your patch (dates, version numbers, etc).<br>
|
|||
|
|
<p>
|
|||
|
|
Regards,<br>
|
|||
|
|
/\/elson<br>
|
|||
|
|
<p>
|
|||
|
|
<i>> If I make my initial changes available in the form of a patch, then in</i><br>
|
|||
|
|
<i>> what form should I make further changes available? A patch to my</i><br>
|
|||
|
|
<i>> patch, or a patch relative to the base code I'm working from (version</i><br>
|
|||
|
|
<i>> 0.83 of the HP backend)? I don't want to require people to apply</i><br>
|
|||
|
|
<p>
|
|||
|
|
<p>
|
|||
|
|
<pre>
|
|||
|
|
--
|
|||
|
|
Source code, list archive, and docs: <a href="http://www.mostang.com/sane/">http://www.mostang.com/sane/</a>
|
|||
|
|
To unsubscribe: echo unsubscribe sane-devel | mail <a href="mailto:majordomo@mostang.com">majordomo@mostang.com</a>
|
|||
|
|
</pre>
|
|||
|
|
<!-- body="end" -->
|
|||
|
|
<p>
|
|||
|
|
<ul>
|
|||
|
|
<!-- next="start" -->
|
|||
|
|
<li> <b>Next message:</b> <a href="0152.html">Petter Reinholdtsen: "Re: sane and video4linux"</a>
|
|||
|
|
<li> <b>Previous message:</b> <a href="0150.html">David Paschal: "Re: Takes really long -- hp-jdex does too"</a>
|
|||
|
|
<li> <b>In reply to:</b> <a href="0149.html">David Paschal: "Re: diff/patch (was: Re: HP OfficeJet Pro,R series support"</a>
|
|||
|
|
<!-- nextthread="start" -->
|
|||
|
|
<!-- reply="end" -->
|
|||
|
|
</ul>
|