On Tue, 27 Jan 2009 14:59:10 +0900 Junichi Uekawa wrote: > At Mon, 26 Jan 2009 22:18:26 +0100, > Francesco Poli wrote: [...] > > On Mon, 26 Jan 2009 06:31:43 +0900 Junichi Uekawa wrote: [...] > > Anyway, could you please clarify what you expect me to write? > > Do you mean I should add something to test_logic.rb or to > > tests/???_*.sh ? > > I tried to perform such tests with a pbuilder hook script > > (B92test-pkg), but some of them failed somehow: I wanted to ask you for > > help in understanding what went wrong, but I thought I could postpone > > that... > > Of course, if I have to add a test, I must understand them now, so I'll > > contact you privately about that. > > Frankly, I don't have a good idea on a regression-testable code. I > was hoping something can be written as test/???_*.sh; or I would have > to manually test it to make sure it hasn't broken.
I hope some test/???_*.sh may be written. I'll contact you privately soon about this. > > > Moreover, how should I proceed with git? [...] > > Is that correct? > > I think you will get conflicts in the master branch that way, because > I may have modified your patch when merging into my repository. You are right! I think I already explained I am a git novice... > > You may want to use feature branches; Mmmmh, topic branches could be a solution. OK, restarting from scratch, I could do as follows: $ git clone git://git.debian.org/git/apt-listbugs/apt-listbugs.git then, inside the repository directory: $ git checkout -b $MY_COOL_BRANCH_NAME origin $ vim onefile $ vim anotherfile $ git add onefile anotherfile $ git commit $ vim thirdfile $ vim anotherfile $ git add thirdfile anotherfile $ git commit $ git format-patch origin -o somedirectory/ And then I could send the patch series to you via e-mail... After some time: $ git checkout master && git pull # this should result in a fast-forward If the patches have been applied to the public repository, then the branch may be discarded: $ git branch -d $MY_COOL_BRANCH_NAME In order to create another topic branch: $ git checkout master && git pull # this should result in a fast-forward $ git checkout -b $SECOND_BRANCH_NAME origin and so forth similarly to $MY_COOL_BRANCH_NAME ... Is that correct? > or better, get a alioth account > so that I can add you to Git committers so you can commit to HEAD > directly. I think I'll need a bit of review from you at first. Later on, when I get more familiar with apt-listbugs package and with packaging practices, I will be ready to commit directly to the repository. -- On some search engines, searching for my nickname AND "nano-documents" may lead you to my website... ..................................................... Francesco Poli . GnuPG key fpr == C979 F34B 27CE 5CD8 DC12 31B5 78F4 279B DD6D FCF4
pgpMzz2lWJgOv.pgp
Description: PGP signature
