Mercurial > hgbook

comparison en/ch11-mq.xml @ 773:3b640272a966

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Progres on resolve
author Bryan O'Sullivan <bos@serpentine.com>
date Sun, 12 Apr 2009 00:05:30 -0700
parents b338f5490029
children ef53d025f410
comparison
equal deleted inserted replaced
772:dbe5f4bb6507 773:3b640272a966
1141 1141
1142 <para id="x_433">Whether you are working on a patch series to submit to a 1142 <para id="x_433">Whether you are working on a patch series to submit to a
1143 free software or open source project, or a series that you 1143 free software or open source project, or a series that you
1144 intend to treat as a sequence of regular changesets when you're 1144 intend to treat as a sequence of regular changesets when you're
1145 done, you can use some simple techniques to keep your work well 1145 done, you can use some simple techniques to keep your work well
1146 organised.</para> 1146 organized.</para>
1147 1147
1148 <para id="x_434">Give your patches descriptive names. A good name for a 1148 <para id="x_434">Give your patches descriptive names. A good name for a
1149 patch might be <filename>rework-device-alloc.patch</filename>, 1149 patch might be <filename>rework-device-alloc.patch</filename>,
1150 because it will immediately give you a hint what the purpose of 1150 because it will immediately give you a hint what the purpose of
1151 the patch is. Long names shouldn't be a problem; you won't be 1151 the patch is. Long names shouldn't be a problem; you won't be