At Mon, 26 Jan 2009 22:18:26 +0100,
Francesco Poli wrote:
> 
> [1  <text/plain; US-ASCII (quoted-printable)>]
> On Mon, 26 Jan 2009 06:31:43 +0900 Junichi Uekawa wrote:
> 
> > Hi,
> 
> Hi!
> 
> > 
> > I'd like something that this code can be tested against, and a real
> > use-case, so I'm waiting for your next patch.
> 
> Well, try to be more explicit next time, please, so that I will be aware
> that you're are waiting for me to do something...  otherwise we could
> find ourselves in a sort of deadlock, waiting for each other's action!

Well, you could have predicted my mind and did it anyway :) 

> 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.

> Moreover, how should I proceed with git?
> I created my commit in my master branch.
> Should I go on as follows?
> 
>   $ git pull   # which will fetch from the public repository
>                # and merge it into my master branch
>   $ 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/
> 
> 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 may want to use feature branches; or better, get a alioth account
so that I can add you to Git committers so you can commit to HEAD
directly.


> 



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to