Bug#935443: [PATCH] dgit-maint-bpo(7): Mention occasional need for --new
Hello, On Sat 14 Sep 2019 at 08:25PM +01, Ian Jackson wrote: >> > dgit-push-adoption(7) >> > ? >> >> What else would go there? > > I'm not sure but I get the feeling that people feel it's hard to get > from where they are now to wher we are advertising that it would be > nice for them to be. I'm too sleepy right now to make much sense on > this point. Fair enough, let's keep the idea in mind. -- Sean Whitton signature.asc Description: PGP signature
Bug#935443: [PATCH] dgit-maint-bpo(7): Mention occasional need for --new
Sean Whitton writes ("Bug#935443: [PATCH] dgit-maint-bpo(7): Mention occasional
need for --new"):
> On Mon 09 Sep 2019 at 01:38PM +01, Ian Jackson wrote:
> > But if you prefer it towards the end then OK.
>
> I don't think it's that odd to put it before TERMINOLOGY but I do think
> it is bad to put it between TERMINOLOGY and the proceeding section.
OK. I will put it between INTRODUCTION and TERMINOLOGY. (And fix the
accidental heading drop.)
> On Mon 09 Sep 2019 at 01:50PM +01, Ian Jackson wrote:
>
> > Maybe what we need instead is
> > dgit-push-adoption(7)
> > ?
>
> What else would go there?
I'm not sure but I get the feeling that people feel it's hard to get
from where they are now to wher we are advertising that it would be
nice for them to be. I'm too sleepy right now to make much sense on
this point.
Regards,
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
Bug#935443: [PATCH] dgit-maint-bpo(7): Mention occasional need for --new
Hello, On Mon 09 Sep 2019 at 01:38PM +01, Ian Jackson wrote: > The text describing the workflows is very long. Many people who read > this manual will already know roughly how to do backports with git and > will already have chosen between the two workflows and will just be > wanting to skim the document to find out how to do it with dgit. > > I thought this bit about --new was important enough to go above all > that. But it felt very odd to put it above TERMINOLOGY which probably > ought to come first. > > But if you prefer it towards the end then OK. I don't think it's that odd to put it before TERMINOLOGY but I do think it is bad to put it between TERMINOLOGY and the proceeding section. On Mon 09 Sep 2019 at 01:50PM +01, Ian Jackson wrote: > Maybe what we need instead is > dgit-push-adoption(7) > ? What else would go there? -- Sean Whitton signature.asc Description: PGP signature
Bug#935443: [PATCH] dgit-maint-bpo(7): Mention occasional need for --new
Ian Jackson writes ("Re: Bug#935443: [PATCH] dgit-maint-bpo(7): Mention
occasional need for --new"):
> The text describing the workflows is very long. Many people who read
> this manual will already know roughly how to do backports with git and
> will already have chosen between the two workflows and will just be
> wanting to skim the document to find out how to do it with dgit.
>
> I thought this bit about --new was important enough to go above all
> that. But it felt very odd to put it above TERMINOLOGY which probably
> ought to come first.
>
> But if you prefer it towards the end then OK.
Hrm.
Maybe what we need instead is
dgit-push-adoption(7)
?
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
Bug#935443: [PATCH] dgit-maint-bpo(7): Mention occasional need for --new
Sean Whitton writes ("Bug#935443: [PATCH] dgit-maint-bpo(7): Mention occasional
need for --new"):
> The text is fine but I don't think it should be inserted between
> TERMINOLOGY and CHOOSING BETWEEN THE TWO WORKFLOWS because those are
> meant to be read together.
>
> How about adding the new section before SEE ALSO?
The text describing the workflows is very long. Many people who read
this manual will already know roughly how to do backports with git and
will already have chosen between the two workflows and will just be
wanting to skim the document to find out how to do it with dgit.
I thought this bit about --new was important enough to go above all
that. But it felt very odd to put it above TERMINOLOGY which probably
ought to come first.
But if you prefer it towards the end then OK.
Thanks,
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
Bug#935443: [PATCH] dgit-maint-bpo(7): Mention occasional need for --new
Hello,
On Sun 08 Sep 2019 at 06:48PM +01, Ian Jackson wrote:
> Sean Whitton writes ("Re: Bug#935443: [PATCH] dgit-maint-bpo(7): Mention
> occasional need for --new"):
>> On Thu 05 Sep 2019 at 04:50PM +01, Ian Jackson wrote:
>> > +=head1 GENERAL TIPS
>> > +
>> > +The first time a package is backported
>> > +for any particular Debian release,
>> > +you will have to pass the --new option to dgit.
>> > +
>> > =head1 CHOOSING BETWEEN THE TWO WORKFLOWS
>> >
>> > If backporting involves making no (additional) changes to the upstream
>> > @@ -59,8 +65,6 @@ work on machines running Debian stable, it is advisable
>> > to choose a
>> > rebasing workflow. This ensures that dgit can automatically update
>> > the debian/patches directory without any manual intervention.
>> >
>> > -=head1 TIPS FOR A MERGING WORKFLOW
>> > -
>>
>> Dropping the =head1 here looks to be an error?
>
> Err, yes. Do you like the rest of the patch ? :-)
The text is fine but I don't think it should be inserted between
TERMINOLOGY and CHOOSING BETWEEN THE TWO WORKFLOWS because those are
meant to be read together.
How about adding the new section before SEE ALSO?
--
Sean Whitton
signature.asc
Description: PGP signature
Bug#935443: [PATCH] dgit-maint-bpo(7): Mention occasional need for --new
Sean Whitton writes ("Re: Bug#935443: [PATCH] dgit-maint-bpo(7): Mention
occasional need for --new"):
> On Thu 05 Sep 2019 at 04:50PM +01, Ian Jackson wrote:
> > +=head1 GENERAL TIPS
> > +
> > +The first time a package is backported
> > +for any particular Debian release,
> > +you will have to pass the --new option to dgit.
> > +
> > =head1 CHOOSING BETWEEN THE TWO WORKFLOWS
> >
> > If backporting involves making no (additional) changes to the upstream
> > @@ -59,8 +65,6 @@ work on machines running Debian stable, it is advisable
> > to choose a
> > rebasing workflow. This ensures that dgit can automatically update
> > the debian/patches directory without any manual intervention.
> >
> > -=head1 TIPS FOR A MERGING WORKFLOW
> > -
>
> Dropping the =head1 here looks to be an error?
Err, yes. Do you like the rest of the patch ? :-)
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
Bug#935443: [PATCH] dgit-maint-bpo(7): Mention occasional need for --new
Hello, On Thu 05 Sep 2019 at 04:50PM +01, Ian Jackson wrote: > +=head1 GENERAL TIPS > + > +The first time a package is backported > +for any particular Debian release, > +you will have to pass the --new option to dgit. > + > =head1 CHOOSING BETWEEN THE TWO WORKFLOWS > > If backporting involves making no (additional) changes to the upstream > @@ -59,8 +65,6 @@ work on machines running Debian stable, it is advisable to > choose a > rebasing workflow. This ensures that dgit can automatically update > the debian/patches directory without any manual intervention. > > -=head1 TIPS FOR A MERGING WORKFLOW > - Dropping the =head1 here looks to be an error? -- Sean Whitton signature.asc Description: PGP signature
Bug#935443: [PATCH] dgit-maint-bpo(7): Mention occasional need for --new
Ian Jackson writes ("[PATCH] dgit-maint-bpo(7): Mention occasional need for
--new"):
> Closes: #935443
> Signed-off-by: Ian Jackson
Rereading the bug description I thought a 2nd patch was needed.
Thanks,
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
Bug#935443: [PATCH] dgit-maint-bpo(7): Mention occasional need for --new
Closes: #935443 Signed-off-by: Ian Jackson --- dgit-maint-bpo.7.pod | 8 ++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/dgit-maint-bpo.7.pod b/dgit-maint-bpo.7.pod index e977d258..e776a478 100644 --- a/dgit-maint-bpo.7.pod +++ b/dgit-maint-bpo.7.pod @@ -47,6 +47,12 @@ If you use a merging backports workflow, your changelog contains entries for each previous upload to B; in a rebasing workflow, it contains only the latest. +=head1 GENERAL TIPS + +The first time a package is backported +for any particular Debian release, +you will have to pass the --new option to dgit. + =head1 CHOOSING BETWEEN THE TWO WORKFLOWS If backporting involves making no (additional) changes to the upstream @@ -59,8 +65,6 @@ work on machines running Debian stable, it is advisable to choose a rebasing workflow. This ensures that dgit can automatically update the debian/patches directory without any manual intervention. -=head1 TIPS FOR A MERGING WORKFLOW - =head2 Use dgit's branches If you do not yourself upload the package to Debian unstable, it is -- 2.11.0
