Hi again,
Osamu Aoki wrote:
> I was lazy to copy that kind of script to the makefile. You can find it
> in maint-guide subversion.
Okay, will take a look.
> On Mon, Apr 25, 2011 at 05:25:31AM -0500, Jonathan Nieder wrote:
>> . The lack of indentation in the source is nice. Less fussy.
>
> That is not my intention. XML makes no distinction. I think it may be
> good idea to run some kind of lint program on XML source.
>
>> . That said, if there were a way to preserve the whitespace of the
>> original and just substitute tags
[...]
> If you want to do this, conversion needs to be done differently with
> much more manual works.
Yes, I understand. What I meant was, given that the whitespace is not
preserved, a non-fussy automatic set of whitespace seems like a nice
default to me.
Alternatives would be to teach debiandoc2dbk some heuristics to save
whitespace in the DOM or to teach it a set of rules that happens to
give the same whitespace as the original. I am not convinced either
would work well.
>> . Sometimes the spacing around closing tags looks unidiomatic, as in
>>
>> ... The detailed
>> procedure for gracefully orphaning a package can be found in the Debian
>> Developer's Reference (see <xref linkend="related"/> ). </para>
>> </footnote>
>
> I noticed this while working on maint-guide conversion. Bug filed.
Thanks (and likewise for the quotation-mark bug).
> I am busy fixing maint-guide now. Please let me know how I get changes
> commited. Access to git branch will be nice.
I think the usual way is for a policy delegate to commit patches or
pull from your repository. I'd encourage doing the following on
alioth to set up a new repository:
mkdir -p ~/public_git
chmod a+xr ~/public_git
git init --bare ~/public_git/policy.git
: >~/public_git/policy.git/git-daemon-export-ok
mv ~/public_git/policy.git/hooks/post-update{.sample,}
and then on your local machine, pushing to it:
echo '[url "os...@alioth.debian.org:/git"]
pushinsteadof = git://git.debian.org' >>~/.gitconfig
echo '[url "os...@alioth.debian.org/public_git"]
pushinsteadof = git://git.debian.org/~osamu' >>~/.gitconfig
git clone git://git.debian.org/dbnpolicy/policy.git
git remote add alioth git://git.debian.org/~osamu/policy.git
... hack hack hack ...
gitk; # everything looks good?
git push alioth master; # yes; publish it.
... hack hack hack ...
gitk --branches; # everything looks good?
# yes; update all branches that already exist remotely.
git push alioth;
Others can browse your history at
http://git.debian.org/?p=users/osamu/policy.git
See http://wiki.debian.org/Alioth/Git#Personal_Git_repository_-_the_morph_way
for details.
To get your work incorporated into the dbnpolicy repository, if it is a
complicated branch you might send an email like
Hi,
Please pull
git://git.debian.org/~osamu master
to get the following changes:
[nice summary comes here]
and the receiving person might run
git pull git://git.debian.org/~osamu master
copying and pasting the URL and branch you specified on the command line.
If it is a simple branch sometimes people instead opt to do
git format-patch origin/master..HEAD
so the patches can be reviewed within an email client and applied with
"git am".
Probably some of the above is already familiar, but I am spelling it
out for reference.
Thanks and hope that helps,
Jonathan
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
