Thanks Guido! I wasn't sure what "upstream" is anymore for this particular code.
Can we add a note somewhere in chapters/intro.sgml about the general
patch submission process? Do you prefer git emails? I was unaware of
email@example.com and that would be a good thing to
document too. Maybe add a "hacking" section to chapters/intro.sgml ?
On Tue, Dec 1, 2015 at 1:42 AM, Guido Günther <a...@sigxcpu.org> wrote:
> On Mon, Nov 30, 2015 at 03:24:10PM -0700, Ken Dreyer wrote:
>> This script is now part of the git-buildpackage utility. Update the link
>> to match.
> Russ is maintaining git-pbuilder on his own page and we're basically
> syncing both ways from time to time so I think we should leave the link
> as is.
> -- Guido
>> bin/git-pbuilder | 4 +++-
>> 1 file changed, 3 insertions(+), 1 deletion(-)
>> diff --git a/bin/git-pbuilder b/bin/git-pbuilder
>> index c1095c0..b7db36c 100644
>> --- a/bin/git-pbuilder
>> +++ b/bin/git-pbuilder
>> @@ -549,7 +549,9 @@ cowbuilder(8), dpkg-buildpackage(1),
>> git-buildpackage(1), pbuilder(8),
>> pdebuild(1), qemubuilder(8), sudo(8)
>> The latest version of this script is available from
>> +L<https://honk.sigxcpu.org/gitweb/?p=git-buildpackage.git>. (Originally this
>> +script was a standalone utility distributed from
>> =head1 AUTHOR
git-buildpackage mailing list